`docker volume prune` Is the Cleanup Command You Use When Old Volumes Keep Surviving and Quietly Hoarding Space You Forgot You Gave Them

Why this command matters: volumes are where Docker clutter gets sneaky because they survive longer than the containers people remember deleting.

If your local Docker setup has been through many projects, databases, and experiments, old volumes may be occupying significant space without any current use. docker volume prune is the targeted cleanup step for that kind of drift.

The command

docker volume prune

This removes unused local volumes.

That matters because volumes are exactly where local databases, caches, search indexes, and other persistent state tend to linger after containers are gone.

Why it helps

It is useful when:

1. disk usage keeps rising after container cleanup
2. old development state is no longer needed
3. Compose stacks have been created and destroyed many times
4. stale volumes are likely cluttering both storage and mental state

Use it deliberately, because deleted volume data is not coming back unless you backed it up somewhere else.

Final recommendation

If Docker cleanup feels incomplete after removing old containers and images, inspect volumes and use docker volume prune when you are sure the unused state is expendable. It is still one of the most practical ways to clear persistent local clutter.

Sources

• Docker volume prune reference