Docker.raw Still Huge After Prune? Check Allocated Space

Check the host file and Docker objects separately

Docker.raw is a sparse VM disk. Its maximum logical size, allocated blocks on macOS and reclaimable objects inside Docker are three different measurements. A large maximum size can remain after successful cleanup without occupying that amount of physical space.

docker context show
docker system df -v
docker_path="$HOME/Library/Containers/com.docker.docker/Data/vms/0/data/Docker.raw"
ls -klsh "$docker_path"
du -sh "$docker_path"
df -h "$HOME"

If the path is missing, find Disk image location in Docker Desktop → Settings → Resources → Advanced. Your version or custom setup can store it elsewhere. With ls -klsh, the leading block count and the logical length answer different questions.

Confirm what prune actually removed

Keep the daemon running. Stop builds before pruning. Use the Docker cleanup guide to choose the category, and compare docker system df before and after. Build cache, images, container writable layers and persistent volumes have different consequences. Do not assume a stopped database container makes its volume disposable.

docker builder prune
# Optional, broader build-cache removal after review:
docker builder prune --all

These commands ask for confirmation and remove build cache; they are not dry runs. Avoid automatic -f flags while learning what a cleanup does. Shared image layers also mean that deleting one image need not release its full displayed size.

Allow time for host-space reclamation

Docker Desktop can return freed VM space to macOS after object removal; timing and behavior depend on its disk format and version. Check allocated host usage again after a short wait. If host allocation stays high, follow Docker’s current Mac FAQ for reclamation guidance instead of assuming that a restart always fixes it.

Do not shrink the capacity slider as a cleanup shortcut

Reducing Docker Desktop’s maximum disk size can recreate the disk image and lose containers/images. Deleting Docker.raw manually is a reset, not selective cache cleanup. Back up important databases and named volumes before any deliberate reset.

Why DevCleaner shows a non-selectable VM row

Docker VM Storage is informational. It shows the host footprint without treating the whole VM as reclaimable or adding it to selected cleanup totals. Choose separate Docker object categories instead. OrbStack and Colima use their own VM files; apply the same distinction between host allocation and Docker objects, then follow the backend’s own storage controls.

FAQ

Why does Docker.raw still show 64 GB after prune?

That can be its logical maximum capacity. Inspect allocated blocks and actual free space rather than using logical file length alone.

Should I delete Docker.raw to free space?

Only as a deliberate reset after backups. It holds the VM storage for containers, images and persistent data; use Docker prune actions for selective cleanup.

References and scope

Reviewed against DevCleaner 1.14.5 and the references below on October 4, 2026. Locations can change with tool versions and custom settings. The examples are inspection steps and deliberate cleanup actions, not a measured claim about how much space your Mac will recover.

• Docker Desktop Mac disk-image FAQ
• Docker build-cache prune