Docker No Space Left on Device Fix

Docker can fill disks with images, build cache, stopped containers, volumes and logs. Check usage before deleting data.

Symptoms

  • Builds fail with no space left on device.
  • Containers cannot write files.
  • Disk looks full after repeated compose builds.

Likely causes

  • Unused images or build cache consume disk.
  • Container logs grow without rotation.
  • Named volumes hold database or app data.

Fix steps

  1. Run docker system df to inspect usage.
  2. Prune unused build cache and images carefully.
  3. Review volumes before deleting anything that may contain data.

Verify the fix

  • Check df -h and df -i.
  • Run docker system df after cleanup.
  • Restart the affected container and watch logs.

FAQ

Is docker system prune safe?

It can delete unused resources. Review flags and volumes before running destructive cleanup.

Can logs fill the disk?

Yes. Configure log rotation for long-running containers.

Related tools and guides

Docker Docker Compose Generator

Generate starter docker-compose.yml snippets for common local development stacks.

 ENV .env Generator

Generate clean .env starter files for local development, app configuration, databases, Redis, mail and API placeholders.

 HTTP HTTP Status Code Explainer

Explain common HTTP status codes with likely causes, API debugging notes and practical verification commands.

 Docker Docker Compose and .env Workflow for Local Development

Local stacks are easier to maintain when docker-compose.yml describes services and .env.example documents configuration without real secrets.

Last updated: May 18, 2026