Running Docker Desktop on a Chromebook.
I run docker in my Chromebook Linux shell and I'm quite happy using the docker CLI however people new to Docker may not be so this is how to run Docker-Desktop on ChromeOS.
Running Linux shell on the Chromebook
Shell up to date (apt update and apt upgrade)
I use the gdebi package to install deb files onto Linux, as dpkg and apt have issues with resolving dependencies
sudo apt install -y gdebi-core
Download the Docker Desktop Deb file
💡 Check the docker Desktop install site for the latest version
make sure the file is in the root of your Linux shell and run
sudo gdebi docker-desktop-4.25.0-amd64.deb
Wait for the installation to complete.
While docker-desktop is installed it won't run at the moment.
💡 If you just launch Docker desktop now it will run however will state that docker services are stopped.
Stop the docker-desktop service
systemctl stop --user docker-desktop
This may take a minute or 2
💡 I didn't use sudo for that command on purpose
Edit the Docker settings.json file
change it from
Save and exit nano
There will now be a docker desktop icon which you can launch.
A service agreement will be displayed
Click on Accept
On the welcome to Docker Desktop screen
choose Continue without signing in
💡 the signing requires pass to be installed which I've not covered here.
You can complete this.
Or click on skip
Wait a couple of minutes for the Service to start
Then it's usable.
If you were already running Docker
If you were already using the docker CLI you may run through this setup and wonder why your running containers are not working.
This is due to Docker context; there are in this case two Docker engines running
sudo docker context ls
will show this
The existing docker cli containers are running in the default context
To view your existing containers in Docker Desktop you will need to shut them down, then run
sudo docker context use desktop-linux
This will swap to the docker-desktop engine/context
Restart your Docker containers
💡 All your containers, images and setup will still be in the default context, so re-running the containers in the desktop-linux context will download the images again, and take up double the space.
All the containers, images etc will now be visible in Docker-desktop
In a previous post
I've used an external mount in the docker-compose.yaml file of
I can't use this on Docker Desktop on the Chromebook, as it needs to be added using the GUI and when I do it writes to the
and adds the file share
which as we say above stops Docker from starting
I'd like to figure out how to get volume mounts working on the Chromebook and I'm not sure if this is an issue with the Linux shell permissions of Docker Desktop trying to be clever.
If you use volume mounts a lot, and need a GUI use Portainer