Docker is eating your Mac's disk
~/Library/Containers/com.docker.docker and routinely
reaches 30-100 GB. Pruning inside Docker frees space in the VM;
shrinking the file itself sometimes needs an extra step.
See what's taking the space
docker system df
Prune safely, in increasing order of aggression
# dangling images + stopped containers + unused networks
docker system prune
# also delete ALL images not used by a running container
docker system prune -a
# build cache (often the biggest offender)
docker builder prune -a
# volumes – ⚠️ this deletes data your containers wrote
docker volume prune
⚠️ prune -a removes every image no container currently
uses – they'll be re-pulled on the next docker run.
volume prune deletes persisted data (databases!) – check
docker volume ls first.
Shrink the VM file
Docker Desktop → Settings → Resources → Disk usage shows the image size and offers cleanup; on recent versions the VM file shrinks automatically after pruning. The nuclear option is Troubleshoot → Reset to factory defaults – it deletes all containers, images and volumes.
Using OrbStack instead?
Same story, different path: ~/Library/Group Containers/HUAQ24HBR6.dev.orbstack.
OrbStack reclaims space more eagerly, but images and volumes still add up.
CacheCleaner shows how big your Docker and OrbStack VM data actually is next to all the other dev caches on the disk – clearly marked with a warning, never selected by default.
Get CacheCleaner for Mac