-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ChromeOS as supported host OS #917
Conversation
On merge of #916 ChromeOS is working and supported. |
5e36ac6
to
986420e
Compare
Hi @ericcurtin thanks! Can we specify that this is inside the "linux mode" of Chromeos and not native? |
Asahi Linux/Fedora Asahi Remix as a host OS also works. But maybe that just falls under Fedora umbrella in general. |
This is paricularly useful in the case of aarch64 Chromebooks, as there is a lack of well upstreamed reasonably priced aarch64 machines. aarch64 Chromebooks fill this gap well. This is using the built in Linux on ChromeOS mode which is debian-based.
986420e
to
7bd889c
Compare
Added @89luca89 |
Thanks! |
Do you have detailed install instructions? |
At present it's just:
in order to install from the HEAD of this git repo. It'll take a while to get to the various distro's packages. In the ChromeOS Linux env of course: https://support.google.com/chromebook/answer/9145439?hl=en Feel free to reach out if you encounter any issues. |
@paulmenzel you have to upgrade to Debian 12 also I forgot to say. You have to do a text replace of "bullseye" to "bookworm" in various /etc/apt files and run "apt dist-upgrade" (maybe a reboot after to be extra safe) if memory serves me right. Google even maintain "bookworm" repos for their tools on this that work great, but they don't seem to have pushed that update to Chromebooks yet. |
It would actually be really cool if Google changed this whole this ChromeOS thing from: ChromeOS -> crosvm/kvm -> Some Linux variant -> lxc/lxd -> Debian -> distrobox -> podman to something like: ChromeOS -> crosvm/kvm -> Some Linux variant -> distrobox with the recent disagreement between Canonical and the ex-Canonical lead maintainers of lxc/lxd. People could choose their guest distro. When lxc/lxd was chosen for ChromeOS, it had an advantage that lxc/lxd could run initful but other containers could not, this is no longer true in podman at least. Would also be one less tool, one less layer of indirection. And tools podman/distrobox are simpler to use and it's easier to switch distros seamlessly. |
This is paricularly useful in the case of aarch64 Chromebooks, as there
is a lack of well upstreamed reasonably priced aarch64 machines.
aarch64 Chromebooks fill this gap well. This is using the built in
Linux on ChromeOS mode which is debian-based.