docker: Error response from daemon: no space left on device
This error matches known, documented patterns with reliable solutions.
Quick Fix (Most Common Solution)
- Run docker system prune
- Remove unused images
Seeing "docker: Error response from daemon: 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
Docker has used all available disk space for images and containers.
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
- Too many images
- Large build cache
- Container logs
How to Fix
- Run docker system prune
- Remove unused images
- Limit log size in daemon.json
Last reviewed: April 2026 How we review solutions
CI/CD Considerations
Registry Authentication and No Space Left On Device in CI Pipelines
No Space Left On Device in CI pipelines is frequently an authentication problem disguised as a network or image error. CI runners do not inherit your local Docker login session and must authenticate explicitly.
For Docker Hub, GitHub Container Registry (GHCR), and AWS ECR, the pattern is the same: add a docker login step before any docker pull or docker build that uses authenticated images. Store credentials as CI secrets — never hard-code tokens in workflow files. For AWS ECR specifically, the authentication token expires every 12 hours, so automated pipelines must re-authenticate on each run using aws ecr get-login-password | docker login. For Docker Hub, use a dedicated bot account with limited permissions rather than a personal account token. Rate limiting is another CI-specific cause: Docker Hub's anonymous pull limit (100/6 hours) is exhausted quickly in CI when many runners pull the same base image. Authenticate even for public images to raise the limit to 200/6 hours, or use GHCR which has no pull rate limits.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 remove?
Stopped containers, unused networks, dangling images.
How to prune everything?
docker system prune -a removes all unused images.
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.