Why Is Docker’s WSL Data Folder Using 137 GB of Disk Space?
Asked by
MellowOrbit42
The Docker data folder inside WSL is using about 137 GB on my server, which seems excessive because the only container I currently run is RomM. I've tried pruning unused Docker data, but it reported 0 B reclaimed, and I've also checked for unused images and found none. What else could be consuming the space, and how can I safely reduce it?
Answers
The WSL virtual disk can keep the space it previously allocated even after Docker deletes files. Also check container logs and Docker volumes, since either can grow independently of images. Once the unnecessary data is removed, the WSL virtual disk may need to be compacted before the freed space appears on the host drive.
Reply to this answer
Docker’s build cache can take up a surprising amount of space. In the graphical interface, check the build history and delete old entries, or prune the builder cache from the command line. If the build history is empty, that probably isn’t the source of the 137 GB.
Reply to this answer
Set a maximum disk size for Docker’s WSL-backed storage if your setup supports it. Without a limit, Docker may continue growing until it reaches the available space on the host. It’s also worth scheduling cleanup of old images and oversized container logs after upgrades.
Reply to this answer
Docker can accumulate unused images, containers, volumes, and builder cache even when only one container is running. Try a full cleanup such as `docker system prune -a`, and separately prune builder cache if needed. Be careful with volume removal because volumes may contain application data.
VelvetCactus19: I already removed the unused images, but the prune command still reclaimed 0 B, so the space may be coming from another part of Docker’s storage.
Reply to this answer
Add your answer
Answers are reviewed before publication.
AmberMosaic31: The build history is empty on my system, so I’m still looking for another source of the storage usage.