Slashdot Mirror
Chrome OS Could Be Getting Containers for Running Linux VMs (zdnet.com)
Chromebook users may soon have a simpler way to run their favorite Linux distribution and applications on Google's Chrome OS hardware. From a report: As spotted by Chrome Unboxed, there's a newly merged commit in Chromium Gerrit describing a "new device policy to allow Linux VMs on Chrome OS." A related entry suggests support could come with Chrome OS version 66, which is due out in stable release around April 24, meaning Google might announce it at its annual IO developer conference, which starts on May 8. Developers can already use a tool called Crouton to install and run Linux on Chrome OS, but there is a security trade-off because Chrome OS needs to be switched to developer mode to use it. There's also a Crouton extension called Xiwi to enable using an OS in a browser window on Chrome OS. However, it too requires developer mode to be enabled. A recent commit suggests Chrome developers are working on a project called Crostini that may solve the developer mode problem by allowing Linux VMs to run inside a container.
I'd rather flash the firmware and then install Cloud Ready, Windows, and GalliumOS. Or at least I would if I cared that much about CrOS. My C720 practically always runs Windows 10, booting into GalliumOS only when I need to unfuck something Windows won't let me unfuck.
How is the Riemann zeta function like Trump rallies? Both have an endless number of trivial zeros.
And better yet, containers and VMs are two ENTIRELY DIFFERENT CONCEPTS.
Docker: LXI Containers
VirtualBox: Hardware Virtualization
These are NOT INTERCHANGEABLE. They may be used as substitutes for each other or in conjunction with each other, but the connotations here are WRONG. Obviously, the "editors" here are too busy blaming things on Russia and Pai to bother checking articles and summaries. Now that I have gone back and reread the summary, I noticed that msmash wrote this which means that she is purely ignorant. Sad.
Well... as someone who still runs solaris (yeah yeah, get over it) I run virtualbox (VM) instances inside Solaris Zones (Proper Containers) on x86_64 (backed by ZFS vols)
This setup has been my daily driver work desktop for years (ie: Run mandated windows SOE desktop, perform vagrant style spin ups of whatever the hell we are fighting then push the images to environment du jour).
You don't run "Linux VMs inside a container", you run processes or Linux distributions inside containers.
I went several layers deep into TFA and I must admit, I'm still confused as to what exactly is being added to ChromeOS, so I wouldn't blame the editors here who are unlikely to be as knowledgeable about the ins and outs of virtualization, containers, UML, chroot, etc.
Here's the problem: The reports claim Google is using both terms. The commit reads this:
Clears it up right? Well, kinda, except according to the same website, crosh has recently had commands added for "running programs inside a container".
This could mean one of eleventeen things. They include:
1. Both LXC style container technology and VMWare style VMs are coming to ChromeOS.
2. Google is using the term "container" to describe some kind of lightweight VM type technology that'll appear in ChromeOS.
5. Google has no idea what VMs are and/or has no idea what containers are, and has confused them, and is planning an LXC style sandboxing environment for ChromeOS.
6. Like 5. but Google knows, it just doesn't care. 9. chromeunboxed is actually making shit up.
I have no idea what the truth is. I'm guessing 6 simply because the low spec of most Chromebooks would make 2 less likely.
You are not alone. This is not normal. None of this is normal.