Chrome OS devices/Crostini

From ArchWiki
< Chrome OS devices(Redirected from Crostini)
Jump to: navigation, search

Crostini is Google's umbrella term for making Linux application support easy to use and integrating well with Chrome OS.

This article describes how to install Arch Linux on a Chromebook in a container (via Crostini), without needing to enable developer mode, allowing apps to run alongside other Chrome/Android apps.

  • Don't need to enable developer mode - Officially supported, leaves ChromeOS secure, no need to flash a BIOS etc.
  • Better battery life - Battery life of Chrome with the functionality of Linux.
  • Access to Android apps, play store etc.
  • No OpenGL support yet (24-11-2018)
  • No sound support yet (24-11-2018)


Enabling Linux support

Look for Linux under Settings and enable it. This installs a Debian Linux container that we will then replace with an Arch Linux container.

Settings > Linux > Enable

Crostini is still rolling out to Chromebooks. If you don't see an option to enable Linux, you may need to switch to the beta or developer channel, if it has not rolled out to the stable channel for your laptop yet. This can be done via Settings > About Chrome OS > Channel > Dev/Beta.

Replacing the default Debian Linux container with Arch Linux

The below instructions were taken from

1. Install an Arch linux container

Open a new terminal in Chrome (Alt + Shift + T). Then connect to terminal and create an arch linux container:

vsh termina --container_name arch --user <gmail username> --lxd_image archlinux/current --lxd_remote

The <gmail username> here is the same user you are logged in to your Chromebooks as, without the and dots. eg. will set --user foobar. Apps launched from the ChromeOS launcher run under this user.

2. Replace the default Debian container with Arch Linux.

The default Debian container is named penguin. Renaming the "arch" container created above to it will cause chrome to launch Linux apps from the arch container.

lxc stop arch
lxc stop penguin
lxc rename penguin debian
lxc rename arch penguin

3. Set password for gmail username

By default the gmail user has no password set. Use lxc exec to set a password:

lxc exec arch -- bash

You also might want to add sudo and add the user to sudoers.

4. Install Crostini container tools, Wayland for GUI apps, XWayland for X11 apps.

First open a console session the the Arch Linux container.

lxc console penguin

Install the cros-container-guest-tools-gitAUR package. Additionally install wayland and xorg-server-xwayland to be able to use GUI tools.

At present (11-24-2018) xkeyboard-config 2.24 break the sommelier-x service. Workaround is to comment out two lines starting with "<i372>" and "<i374>" in /usr/share/X11/xkb/keycodes/evdev. Then enable and start the services.

$ systemctl --user enable sommelier@0      # For Wayland GUI apps
$ systemctl --user enable sommelier-x@0    # For X11 GUI apps
$ systemctl --user start sommelier@0      # For Wayland GUI apps
$ systemctl --user start sommelier-x@0    # For X11 GUI apps

Make sure these services are running successfully by running:

$ systemctl --user status sommelier@0
$ systemctl --user status sommelier-x@0

Now, when apps are installed in Arch Linux, they will automatically show up and can be launched from ChromeOS. Note that while GUI apps work, rendering is still software, with no OpenGL support yet.

Known issues

Tested, working (2018-11-24)

  • Pycharm

Tested, not working (2018-11-24 - no hardware acceleration, audio)

  • Gnome (No OpenGL)
  • glxgears (No OpenGL)
  • Audacity (No recording devices)


Network not working on Pixelbook reports that the below setting needs to be set to get the network working on the pixelbook. Make sure to restart your container after you set it.

lxc profile set default security.syscalls.blacklist "keyctl errno 38"

DNS resolution not working

DNS resolution stopped working in the container after my install. To get it working again I had to create /etc/resolv.conf.

App not opening in chrome OS (infinite spinner)

I found that launching a console (lxc console penguin) session prevents apps from launching in Chrome OS. Launching results in an infinite spinner. In that case I have to stop and start the container to get the Chrome OS launcher working

lxc stop penguin
lxc start penguin

Instead of using an lxc console session, I use a regular Linux terminal GUI launched from ChomeOS that prevents this issue.