Quick Answer: This is different from Linux failing to install in the first place — here, Crostini was working before, but the container now fails to start with an error like “failed to start container” or the terminal window closing immediately. It’s usually caused by the container losing sync with ChromeOS after an update, low storage space, or a corrupted container image. Restarting the Chromebook and checking free storage fixes most cases; resetting just the Linux container fixes the rest.
What Causes This Error
- A ChromeOS update changing the underlying VM version in a way the existing container doesn’t match
- Storage running critically low, which prevents the container from allocating space it needs to start
- The container image itself becoming corrupted after an improper shutdown or crash
- A stuck background process from a previous session still holding the container’s resources
How to Fix It
Step 1: Restart the Chromebook
A simple restart clears most stuck container states and resolves this more often than any other single step, especially right after a ChromeOS update.
Step 2: Check your available storage
Go to Settings > Device > Storage management. The Linux container needs free space to start correctly; if storage is nearly full, clear out large files or unused apps and try again.
Step 3: Try starting Linux from Settings instead of the terminal shortcut
Go to Settings > Advanced > Developers > Linux development environment and check its status there. Sometimes the terminal app shortcut is stale even though the underlying container can still be reached through Settings.
Step 4: Reset just the Linux container (not a full Powerwash)
In Settings > Advanced > Developers > Linux development environment, choose Remove Linux development environment. This deletes the container and any files stored only inside it, but keeps the rest of the Chromebook untouched. Reinstall Linux fresh afterward — see how to install Linux on a Chromebook.
Step 5: Back up container files first if possible
Before resetting, if the terminal opens even briefly, copy any important files out of the Linux files folder in the Files app. Once you remove the container, anything stored only inside it is gone for good.
Still Not Fixed?
If resetting the container and reinstalling Linux from scratch still fails to start, the issue is more likely a hardware or ChromeOS support limitation than a container problem — check whether your specific model and current ChromeOS version still officially support Linux, since support was removed on a handful of older devices.
FAQ
Will resetting the Linux container delete my Chromebook’s regular files?
No. It only removes the Linux container and files stored specifically inside it, not your Downloads, Drive files, or other ChromeOS data.
Is this the same problem as Linux failing to install the first time?
No. That’s typically a storage, virtualization support, or hardware compatibility issue during first setup. This article covers Linux breaking after it was already working. See Linux (Crostini) won’t install or start if you’ve never gotten it running at all.
Does a ChromeOS update always break Linux?
No, most updates are fine. But major version jumps occasionally require the container to be recreated, which is why a restart or container reset often resolves it after a big update.
