11–20 of 140 posts
I can't wait for the day that phone operating systems development environments are a docker pull away. It's encouraging to see Google approaching my ideal workflow using containerisation. Apple systems are great until you run into the garden walls and are forced to use closed-source single platform software like Xcode. Chrome OS and Android are a lot more open in many respects. Hopefully efforts like this continue wi…
Interesting to see Chrome OS adopt process compartmentalization techniques such as this, specifically adopting `cgroups'. Afaik, cgroups isn't enabled by default and requires customizing the kernel before you can enable it. At the very least, container tools such as Docker require symlinks too to invoke chroot-like filesystem isolation and this is also not available. It'll interesting to see where they'll go with thi…
No, cgroups is enabled on every major linux distro (though I'm too lazy to check if every configurable is set such that it will run this particular Android container). It's well-established base linux technology at this point, certainly nothing weird.
I wonder how hard it would be to get this working on, say, Fedora... At the very least, one would need to replace what sounds like a surfaceflinger wayland proxy.
Interesting to see Chrome OS adopt process compartmentalization techniques such as this, specifically adopting `cgroups'. Afaik, cgroups isn't enabled by default and requires customizing the kernel before you can enable it. At the very least, container tools such as Docker require symlinks too to invoke chroot-like filesystem isolation and this is also not available. It'll interesting to see where they'll go with thi…
Speaking of which, it is now possible to run full linux and android apps on chromebooks which support containers (and vms?) in a tab with the new official Google Crostini project. Makes the Pixelbook more attractive. https://twitter.com/rothgar/status/981579699833880576 More info on Crostini https://www.reddit.com/r/chromeos/comments/7ytpb1/project_cr... …
I wonder how hard it would be to get this working on, say, Fedora... At the very least, one would need to replace what sounds like a surfaceflinger wayland proxy.
Just boot, launch a chrome window and type Ctrl alt t.
Then type vmc start dev.
Then you can use whatever distribution you want as you have full GNU/Linux.
Only works on Pixelbooks but Google will extend and will share more at Google IO.
You can even package up gnu/Linux applications. One click and they run in a container but on a second Linux kernel.
So Android shares the ChromeOS kernel where gnu/Linux will run in a container on top of a VM using the KVM.
It is interesting that Google did not feel just using containers for GNU/Linux was secure enough.
I can't wait for the day that phone operating systems development environments are a docker pull away. It's encouraging to see Google approaching my ideal workflow using containerisation. Apple systems are great until you run into the garden walls and are forced to use closed-source single platform software like Xcode. Chrome OS and Android are a lot more open in many respects. Hopefully efforts like this continue wi…
You have it with ChromeOS 67. Docker without having to put in developer.
Earlier quoted context omitted.
No, cgroups is enabled on every major linux distro (though I'm too lazy to check if every configurable is set such that it will run this particular Android container). It's well-established base linux technology at this point, certainly nothing weird.
I think OP might be referring to the fact that Android kernels disable most functionality required to run most standard Linux container tech. AFAIK it's not possible to run Docker even on rooted devices if they are running a (close to) vanilla kernel, whereas you can run Docker just fine on Linux single board computers that run similar processors.
But now with ChromeOS 67 no longer need to use developer to do.
Then install the Android XSDL app for the GUI.
I wonder how hard it would be to get this working on, say, Fedora... At the very least, one would need to replace what sounds like a surfaceflinger wayland proxy.
Very easy with ChromeOS 67. Just boot, launch a chrome window and type Ctrl alt t. Then type vmc start dev. Then you can use whatever distribution you want as you have full GNU/Linux. Only works on Pixelbooks but Google will extend and will share more at Google IO. You can even package up gnu/Linux applications. One click and they run in a container but on a second Linux kernel. So Android shares the ChromeOS kernel…
Earlier quoted context omitted.
No, cgroups is enabled on every major linux distro (though I'm too lazy to check if every configurable is set such that it will run this particular Android container). It's well-established base linux technology at this point, certainly nothing weird.
I think OP might be referring to the fact that Android kernels disable most functionality required to run most standard Linux container tech. AFAIK it's not possible to run Docker even on rooted devices if they are running a (close to) vanilla kernel, whereas you can run Docker just fine on Linux single board computers that run similar processors.
I took the point to be "cgroups is weird, nonstandard and by implication dangerous" when the truth is more "cgroups is standard equipment, sorta boring, and the obvious way to implement a container like this".