Chromebook Linux Container Won't Start? How to Fix
Short answer: If your Chromebook's Linux container will not start, begin with a restart, then check storage and updates. A full disk, an interrupted ChromeOS update, or a policy that disables Linux are the usual causes. Update Linux packages with `sudo apt-get update && sudo apt-get dist-upgrade`. If the container still will not open, back up your files, remove the container, and set it up again. Most devices recover with these steps.
Why the Linux container fails to start
The Linux container on a Chromebook runs inside ChromeOS in a sandbox. Google's Linux setup page states that all Linux apps run inside the same sandbox, so a problem in the container can affect other Linux apps but not the rest of your Chromebook. When the container will not start, the cause is usually one of a few common issues: not enough storage, a pending update, or a policy that disabled Linux.
Google's own guidance for Linux problems starts with two steps: restart your Chromebook, and update your packages. The setup page recommends running `sudo apt-get update && sudo apt-get dist-upgrade` from the Terminal. Most failures clear with these steps. Only a smaller number require removing and recreating the container.
Restart your Chromebook first
Restarting is the most reliable first step. Google's update help page explains that your Chromebook automatically checks for updates and downloads them when it connects to the internet, and that you need to restart to finish an update. If the update was interrupted, the Linux container may fail to start until the system has fully rebooted.
ChromeOS also performs a self-check at startup. Google's Auto Update policy page notes that if the system detects it has been tampered with or corrupted, it typically repairs itself and reverts to its original state. Restart once, then try opening a Terminal window again.
Free up storage space
A full disk is one of the most common reasons a Linux container will not start. The container needs room to write its filesystem and run its processes. Chromebooks with lower-capacity storage can fill up quickly, especially if you install several Linux packages, keep large downloads, or store many files in the container's home directory.
Check your storage in the Files app or in Settings, then remove what you no longer need. The free-up-storage guide walks through your options. If you think the container itself is the issue, the container running out of space guide covers that case in more detail.
Update ChromeOS and Linux packages
Both ChromeOS and the Linux container receive updates. Google's Linux setup page suggests running `sudo apt-get update && sudo apt-get dist-upgrade` when Linux or Linux apps misbehave. It also notes that Linux automatically checks for new packages after initial setup and every 24 hours while it is running, so an up-to-date container is less likely to fail.
ChromeOS updates matter just as much. Open Settings, select About ChromeOS, then Check for updates. Google's update page says your Chromebook will start downloading an update automatically if one is found. Restart when prompted. Most Chromebooks receive updates for 10 years; a device past its update date may simply be too old, and the update check guide shows how to confirm where your device stands.
Check administrator settings
If your Chromebook is managed by a school or employer, Linux can be disabled by policy. Google's Linux setup page says that if you use your Chromebook at work or school, you might not be able to use Linux, and you should contact your administrator in that case. The Linux development environment toggle lives under Settings, About ChromeOS, Developers. If it is grayed out or missing, a policy is blocking it.
On an unmanaged device, confirm that Linux was actually enabled during setup. Google notes that setup can take 10 minutes or more. If you interrupted it, the container may be incomplete. Try turning Linux off and on again from the same Developers panel.
Back up, remove, and reinstall the container
If restarting, freeing storage, and updating do not help, the next step is to remove the container and start over. Before removing it, back up your Linux files. Google's Linux help section points to a backup and restore guide for Linux files and apps. Your container's home directory is the main thing to preserve, and you will want to save it before any destructive step.
To remove the container, go to Settings, About ChromeOS, Developers, select Linux development environment, then Remove. After removal, set up Linux again from the same panel. You will get a fresh Debian environment and can reinstall your tools. The enable Linux guide walks through the setup process, and the Linux backup guide shows how to protect your files first.
If a fresh container still will not start, a deeper reset may be needed. Powerwash vs recovery explains the difference between the two, and the recovery USB guide covers making recovery media. Both clear local data, so back everything up before you go this far.
What to look for in a new Chromebook
If your Chromebook is old or has little storage, a new device may be the more practical fix. Linux development benefits from more RAM and faster, larger storage. Google's Chromebook Plus page states that Plus models get 8 GB or more of RAM and 128 GB or more of storage, which gives the Linux container room to breathe. That tier is worth considering if you use Linux regularly.
For storage, think about your workload. A 64 GB model can run Linux, but 128 GB or 256 GB leaves more headroom for containers, tools, and downloaded packages. If you run heavy builds or multiple services at once, pay attention to RAM as well. The buying guides on this site compare current models by specs.
What to pick for your use
| If you | Pick | Buying guide |
|---|---|---|
| You run a few command-line tools occasionally | 64 GB or more storage | Best 64 GB Chromebooks in 2026: 15 Picks Compared on Specs |
| You run code editors, local servers, and several packages | 128 GB or more storage | Best 128GB Chromebooks 2026: 13 Picks |
| You build large projects and want comfortable headroom | 256 GB storage | Best 256 GB Chromebooks in 2026: 11 Picks Compared on Specs |
| You want the Chromebook Plus baseline of 8 GB RAM and 128 GB storage | A Chromebook Plus model | Best Chromebook Plus 2026: 15 Picks Compared on Specs |
Questions
Why will my Linux container not start?
The common causes are a full disk, an interrupted ChromeOS update, outdated Linux packages, or a policy that disables Linux on managed devices. Restart your Chromebook first, then check storage and updates.
Do I have to reinstall Linux if the container will not start?
Not always. Google's Linux setup page recommends restarting your Chromebook and running `sudo apt-get update && sudo apt-get dist-upgrade` first. If those steps fail, removing and recreating the container usually works.
Will removing the Linux container delete my files?
Removing the container erases its local files. Google points to a backup and restore guide for Linux files and apps, so back up your home directory before you remove it.
Can a school or employer block Linux?
Yes. Google's Linux setup page says that if you use your Chromebook at work or school, you might not be able to use Linux, and you should contact your administrator if the option is unavailable.
How much storage do I need for Linux on a Chromebook?
The Linux container needs room for its filesystem and your tools. Google's Chromebook Plus page specifies a baseline of 8 GB of RAM and 128 GB of storage for Plus models, and that tier leaves comfortable headroom for most development work.
What changed
- : First published.