The WSL Docker data directory on my server has grown to about 137 GB, which seems excessive because the only container I currently run is RomM. I've tried pruning and removing unused images, but pruning reports that it would recover 0 B. The build history is also empty. What else could be using the space, and how can I safely reduce it?
4 Answers
It’s worth setting up occasional maintenance: remove old images after upgrades, prune unused builder cache, and rotate or delete old container logs. Be careful with volumes, since pruning them can erase application data if they are not backed up.
If images and build cache are not the problem, check persistent volumes and container logs. Applications can write large databases, artwork, caches, or media files into volumes, while verbose JSON logs can also grow very large. Inspect the Docker data directory and use Docker’s disk-usage commands to identify the specific volume or container before deleting anything.
Docker can accumulate unused images, stopped containers, builder cache, volumes, and container logs. Try checking what is actually consuming the space with `docker system df -v`, then remove anything you no longer need. A broader cleanup is `docker system prune -a`, but review the resources first because it can remove unused images and stopped containers.
I already removed the unused images, and the normal prune command reports that it would free 0 B.
Docker Desktop’s virtual disk is usually allowed to grow until the host runs out of space. Set a maximum disk size in Docker Desktop so the WSL-backed data file cannot expand without limit. This controls the virtual disk, though it does not automatically clean up data already stored inside it.
I checked the build history and it’s empty, so the space is probably coming from a volume, logs, or application data rather than cached builds.