Docker and OrbStack Disk Bloat on a Mac (2026 Cleanup Guide)

Docker and OrbStack Disk Bloat on a Mac (2026 Cleanup Guide)
Short answer

Docker Desktop stores everything in a single virtual disk image (Docker.raw) that grows but never automatically shrinks — pruning frees space inside it, but you may need to compact it to return space to macOS. OrbStack is thin-provisioned and gives space back more readily. Either way, unused images, build cache and volumes are re-pullable, so pruning them is safe.

Why containers eat so much disk

Every image layer, stopped container, named volume and build-cache entry is kept until you explicitly remove it. On an active machine in 2026, that's routinely 30–80 GB — and most of it is images you pulled once for a project you've since finished.

Docker's disk image never shrinks on its own

Docker Desktop keeps its data inside one big file:

~/Library/Containers/com.docker.docker/Data/vms/0/data/Docker.raw

Here's the gotcha that catches everyone: deleting images frees space inside that file, but the file itself stays large on your Mac. To actually return the bytes to macOS you prune first, then compact:

Prune removes anything not currently in use. If you have a stopped container or volume you still need, back it up first — but images and build cache always re-pull.

OrbStack handles it better

OrbStack, the popular lighter alternative, stores its data under ~/.orbstack and is thin-provisioned, so it releases space more gracefully. It still accumulates images, though — the same prune habits apply:

docker system prune -a (OrbStack is Docker-compatible), or manage images in the OrbStack app. If you've fully switched away from Docker Desktop, deleting its leftover Docker.raw can reclaim a large one-time chunk.

Don't forget the sibling caches

Container work rarely travels alone. The same machine usually also has node_modules and package caches, Xcode DerivedData, and increasingly local AI models. Sweeping all of them together is where a developer Mac gets 100 GB back.

MacCleaner measures the container footprint alongside those other groups, shows real sizes before you touch anything, and keeps cleanups recoverable.

Frequently asked questions

Why doesn't my disk space come back after docker system prune?

Because Docker Desktop stores data in a virtual disk image (Docker.raw) that shrinks inside but not on disk. Prune frees internal space; compact or delete the image to return it to macOS.

Is docker system prune safe?

It removes unused images, containers, networks and (with --volumes) volumes. Images and build cache re-pull safely; back up any stopped container or volume you still need first.

Does OrbStack use less disk than Docker Desktop?

Generally yes — it's thin-provisioned and returns freed space more readily. It still accumulates images over time, so periodic pruning still helps.

See where your space actually went

MacCleaner scans read-only, shows you every file before anything is touched, and lets you choose Trash or permanent. Free for up to 500 MB of cleanup a day.

Download for Mac