How to fix write /var/lib/docker/tmp/...: no space left on device in Docker

DockerBEGINNERMEDIUMUpdated Dec 1, 2025· 150 views

This error occurs when Docker runs out of disk space during an image build. The Docker daemon cannot write temporary files or layer data because the partition hosting /var/lib/docker is full.

Quick fix

Fixes ENOSPC

# Check disk space on all partitions
df -h

# Check Docker-specific disk usage
docker system df

# For detailed breakdown
docker system df -v
  1. Check current disk usage
  2. Clean up unused Docker resources
  3. Remove build cache specifically
  4. Remove dangling volumes
docker — error
# Check disk space on all partitions
df -h
# Check Docker-specific disk usage
docker system df
# For detailed breakdown
docker system df -v
write /var/lib/docker/tmp/...: no space left on device

What this error means

When Docker builds an image, it creates temporary files and stores layer data in /var/lib/docker. If this partition runs out of space, the build fails with "no space left on device." This is one of the most common Docker errors, especially on development machines and CI/CD servers where images and containers accumulate over time. Docker does not automatically clean up unused images, containers, volumes, or build cache, so disk usage grows until it hits the limit. The error can also occur if the filesystem runs out of inodes (even with free disk space) or if Docker is configured with disk quotas that have been exceeded.

Typical symptoms

  • Docker build fails with 'no space left on device' error
  • Error message references /var/lib/docker/tmp or layer files
  • docker pull commands fail when downloading images
  • Containers fail to start with write errors
  • The df -h command shows the Docker partition at 100% usage
  • CI/CD pipelines fail during the build step

Common causes

  1. Accumulated unused Docker images consuming disk space
  2. Build cache from previous builds filling up storage
  3. Stopped containers with large writable layers not removed
  4. Dangling (orphaned) volumes taking up space
  5. Large build context being copied into the image
  6. Multi-stage builds not properly cleaning intermediate layers
  7. Inode exhaustion (many small files consuming all inodes)
  8. Docker configured with a disk space limit that has been reached

How to fix "write /var/lib/docker/tmp/...: no space left on device"

1Check current disk usage

First, identify how much space Docker is using and what's consuming it:

bash
# Check disk space on all partitions
df -h

# Check Docker-specific disk usage
docker system df

# For detailed breakdown
docker system df -v

This shows space used by images, containers, volumes, and build cache. The output helps you decide what to clean up.

2Clean up unused Docker resources

The quickest fix is to remove all unused Docker objects:

bash
# Remove stopped containers, unused networks, dangling images, and build cache
docker system prune -f

# Also remove all unused images (not just dangling ones)
docker system prune -a -f

Note: This does NOT remove volumes by default to prevent data loss. If you're sure you don't need orphaned volumes, add the --volumes flag.

3Remove build cache specifically

Build cache can consume significant space. To clear it:

bash
# Remove all build cache
docker builder prune -a -f

# Remove only cache older than 24 hours
docker builder prune --filter until=24h -f

After clearing, run docker system df again to verify space was reclaimed.

4Remove dangling volumes

If the standard prune didn't free enough space, target volumes specifically:

bash
# List all volumes
docker volume ls

# Remove volumes not used by any container
docker volume prune -f

# Remove a specific volume
docker volume rm <volume_name>

Warning: Only do this if you're certain the data in those volumes is not needed.

5Remove specific images and containers

For more targeted cleanup:

bash
# List all images with sizes
docker images -a

# Remove a specific image
docker rmi <image_id>

# Remove all exited containers
docker rm $(docker ps -aq -f status=exited)

# Remove all containers (careful!)
docker rm -f $(docker ps -aq)

Use docker images --format "{{.Repository}}:{{.Tag}} {{.Size}}" to see image sizes and identify the largest ones.

6Optimize your Dockerfile

Prevent future issues by reducing image size:

Use multi-stage builds:

dockerfile
# Build stage
FROM node:20 AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build

# Production stage - only copies what's needed
FROM node:20-alpine
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
CMD ["node", "dist/index.js"]

Use .dockerignore:
Create a .dockerignore file to exclude unnecessary files from the build context:

bash
node_modules
.git
*.md
tests
.env*

This reduces both build time and disk usage.

7Check for inode exhaustion

Sometimes the disk has free space but is out of inodes:

bash
# Check inode usage
df -ih

If inodes are at 100% but disk space is available, you have many small files. This can happen with node_modules or cache directories. Clean up small files or move to a filesystem with more inodes.

8Move Docker data to a larger partition

If you frequently run out of space, move Docker's data directory:

bash
# Stop Docker
sudo systemctl stop docker

# Move the data
sudo mv /var/lib/docker /path/to/new/location/docker

# Update Docker configuration
sudo nano /etc/docker/daemon.json

Add or update the data-root setting:

json
{
  "data-root": "/path/to/new/location/docker"
}

Then restart Docker:

bash
sudo systemctl start docker

Alternatively, use a symlink:

bash
sudo ln -s /path/to/new/location/docker /var/lib/docker

Advanced notes

Automated cleanup in CI/CD:
Add cleanup steps to your CI pipeline to prevent disk exhaustion:

yaml
# Example GitLab CI
after_script:
  - docker system prune -f

Docker Desktop (Windows/Mac):
Docker Desktop uses a virtual disk image that can grow but doesn't automatically shrink. To reclaim space:
- Mac: Remove and recreate the Docker.raw file (Settings > Resources > Advanced > Disk Image Location)
- Windows: Use "Reset to factory defaults" in Docker Desktop settings, or manually shrink the WSL2 virtual disk

Monitoring Docker disk usage:
Set up alerts before you run out of space:

bash
# Simple script to check Docker disk usage
USAGE=$(docker system df --format '{{.Size}}' | head -1)
echo "Docker is using: $USAGE"

Setting up automatic cleanup with cron:

bash
# Add to crontab -e
0 0 * * * docker system prune -af --filter "until=168h"

This removes unused resources older than 7 days, daily at midnight.

Overlay2 storage driver considerations:
The overlay2 storage driver (default on modern systems) is more efficient than aufs or devicemapper. Check your driver with:

bash
docker info | grep "Storage Driver"

For Kubernetes/container orchestration:
If running many containers, consider using local ephemeral storage limits and monitoring with Prometheus + cAdvisor.

Frequently asked questions

What does "ENOSPC" mean?
When Docker builds an image, it creates temporary files and stores layer data in /var/lib/docker. " This is one of the most common Docker errors, especially on development machines and CI/CD servers where images and containers accumulate over time. Docker does not automatically clean up unused images, containers, volumes, or build cache, so disk usage grows until it hits the limit.
How do I fix "ENOSPC"?
This error occurs when Docker runs out of disk space during an image build. The Docker daemon cannot write temporary files or layer data because the partition hosting /var/lib/docker is full.
What causes "ENOSPC"?
Accumulated unused Docker images consuming disk space Build cache from previous builds filling up storage Stopped containers with large writable layers not removed
Is the "ENOSPC" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading