Error: ENOSPC: no space left on device
This error matches known, documented patterns with reliable solutions.
Quick Fix (Most Common Solution)
- Run docker system prune -a
- Clear build cache with docker builder prune
Seeing "Error: ENOSPC: no space left on device"? This error can be frustrating, but it's usually fixable. It typically affects your development workflow or system. Below you'll find clear, step-by-step solutions to resolve this issue.
What This Error Means
The disk is completely full.
Frequently documented in developer and vendor support forums.
Not affiliated with browser, OS, or device manufacturers.
New here? Learn why exact error messages matter →
Common Causes
- Docker images filling disk
- Build cache too large
- Logs filling disk
How to Fix
- Run docker system prune -a
- Clear build cache with docker builder prune
- Remove large unused images
Last reviewed: June 2026 How we review solutions
Didn't fix it? Get a personalised solution
Version Notes
Docker Engine Versions and ENOSPC NO SPACE Behavioral Differences
ENOSPC NO SPACE because core behaviors around networking, storage drivers, and BuildKit availability changed across major releases. Code that works on Docker 20.x may fail on Docker 24.x or vice versa.
Check your Docker version with docker version — the output includes both client and server (daemon) versions, which may differ in remote environments. Docker Compose V2 (bundled as docker compose) replaced the standalone V1 (docker-compose) in 2023 and has subtle behavioral differences: the depends_on condition field, variable expansion in environment values, and profile behavior all changed. If your Compose file uses features from V2 but the environment has V1, commands may silently behave differently and produce ENOSPC NO SPACE. Pin the Docker Compose version in CI with docker compose version checks. For production deployments, test Docker Engine upgrades in staging first — storage driver migrations (overlay2, devicemapper) are not always automatic and can cause data access errors resembling ENOSPC NO SPACE.Optional follow-up
Some users ask whether saving fixes for recurring errors would be useful when the same issue appears again.
Was this explanation helpful?
Frequently Asked Questions
What does prune -a do?
Removes all unused images, not just dangling ones.
How do I prevent this?
Set up regular pruning with cron or use Docker cleanup policies.
Related Resources
Also Known As
- Docker container error
- Docker build failure
- Container runtime error
- Docker daemon error
Common Search Variations
- "docker container won't start"
- "docker build error fix"
- "docker image not found"
- "container exited with error"
- "docker daemon not responding"
- "fix docker network error"
Related Errors
Still Stuck?
Paste a different error message or upload a screenshot to get help instantly.