ChromeOS 75.0.3770.10 Rolling out to the Dev Channel – Enables VPN Support in Crostini and other Fixes
Google is currently pushing ChromeOS 75.0.3770.10 to users on the Dev channel. Software developers and Road Warriors all over will start to rejoice when they hear that Crostini containers will finally route connections through a VPN if active on your Chromebook.
Disclaimer: This Page Has Been Archived
Please note that this blog post has been archived and may contain information that is outdated, defunct, or covers topics that are no longer of interest. It is being kept available solely for reference purposes, in case others might find portions of it useful.
For more recent and up-to-date tutorials, I recommend visiting KMyers.me or other websites that specialize in the topic you are interested in. It is always advisable to seek the most current information to ensure accuracy and relevance.
This update seems to be very smooth, I ran into no issues with starting Android or Linux applications.
ChromeOS VPN Support in Crostini
I created a blog post about an hour ago saying that the next release of ChromeOS will enable VPN support in Crostini and said the release could happen at any moment, well, about 40 minutes later, that moment has come. Your Linux container will now route traffic over a VPN if you have a VPN running on your Chromebook. This includes both VPNs setup in the ChromeOS VPN settings and Android VPNs! I have personally tested this using the OpenVPN application on Android connecting to my personal VPN and it worked flawlessly.
There are no flags to enable, it just works.
New Folders in File Manager
There is now a folder for “Bug Reports” and a Android Application that I have installed (termux) showing in the File Manager. Clicking on “Bug Reports” brings up a empty folder that is read only but the Termux folder shows the storage area of Termux.
Crostini Installer Disk Space Check
Google has added a disk space check into the Crostini installer to verify adequate disk space before installing the Termina VM and Crostini container. In the past, the installation would act like it was working and eventually fail.
Google is now collecting some basic metrics during the installation of Crostini to help them understand the reasons for installation failure. This allows Google to see the following
- Disk Space
- Download Times
- Installation Errors
Note : Google DOES NOT have the ability to see anything that happens inside of the container, you can view the source code here if so inclined.
Architecture Check During Crostini Import
It was theoretically possible to take a backup generated on a X86_64 Chromebook and import it on a Arm Chromebook. The resulting mess will have a lot of problems that may render the container unusable. Google has implemented a change to add a architecture check before importing a backup.