`docker system df` Is the Command You Should Run Before You Say Docker Ate Your Disk Without Being Able to Prove Where It Went
A practical guide to `docker system df` for inspecting Docker disk usage by images, containers, local volumes, and build cache before cleanup becomes random and destructive.
Why this command matters: saying “Docker is taking too much space” is not yet a diagnosis. It is a complaint that needs numbers.
If your machine is getting tight on storage, docker system df is one of the best first commands because it gives you a category-level breakdown of what Docker is consuming.
The command
docker system dfThis reports usage across:
- images
- containers
- local volumes
- build cache
That immediately tells you which cleanup direction is most likely to matter.
Why it helps
Without this, developers often clean blindly:
- prune images when volumes are the real hog
- delete containers while build cache remains massive
- overreact with broad destructive cleanup
docker system df gives you the map before you start deleting things.
Final recommendation
If Docker disk usage feels out of control, inspect it first with docker system df. It is still one of the fastest ways to replace vague frustration with a concrete cleanup target.