Guide 6 Jun 2026 6 min read

How to Clean Docker on macOS and Reclaim Gigabytes

Docker is one of the biggest silent disk-space hogs on a developer Mac. Every docker build, docker pull, and docker-compose up layers images, containers, and volumes onto your drive. Old versions, dangling layers, and forgotten containers pile up fast. It is common for Docker Desktop alone to consume 10–50 GB before you even notice.

The good news: nearly everything Docker stores is rebuildable or re-pullable. The bad news: Docker’s CLI commands are powerful but destructive — one wrong flag can wipe data you still need. This guide shows you the safe manual approach, then the one-click alternative.

What Docker Hoards on Your Mac

On macOS, Docker Desktop stores everything inside a single virtual disk image:

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

Inside that image, Docker keeps four categories of data:

Images — downloaded base images and every layer from your own builds
Containers — stopped containers still retain writable layers and logs
Volumes — named volumes that persist data outside container filesystems
Build cache — intermediate layers from BuildKit multi-stage builds

Method 1: The Surgical (Safe) CLI Approach

Step 1 — See what Docker is holding

docker system df

This prints a tidy summary of images, containers, volumes, and build cache — exactly how much each category is using. If you see Images at 15 GB and Containers at 8 GB, you know where to focus.

Step 2 — Remove dangling images

Dangling images are layers no longer tagged or referenced by any container. They are 100% safe to delete:

docker image prune

Add -f to skip the confirmation prompt:

docker image prune -f

Step 3 — Remove stopped containers

Every container you have ever started and stopped is still sitting on disk. Clean them all at once:

docker container prune -f

⚠️ Warning

This removes all stopped containers. If you have stopped containers with data you want to keep, back them up or start them first.

Step 4 — Remove unused volumes

Named volumes survive even when their containers are deleted. Prune only the ones not attached to any running container:

docker volume prune -f

Step 5 — The nuclear option (use with care)

If you want to wipe everything — images, containers, volumes, networks, and build cache — in one shot:

docker system prune -a --volumes

The -a flag also removes images not currently used by a running container. This is the fastest way to reclaim space, but you will have to re-pull or rebuild everything afterward.

Method 2: Docker Desktop GUI

If you prefer a graphical approach:

Open Docker Desktop
Click the Settings (gear) icon
Navigate to Disk usage
Click Clean up next to images, containers, or volumes

This is safer than CLI because it surfaces exactly what will be deleted, but it is slower if you manage many projects across different contexts.

Method 3: One-Click with Bytegone

If you want to reclaim Docker space alongside Xcode DerivedData, npm caches, browser data, and logs — all in one pass, without memorizing flags or touching Terminal — Bytegone does it in one click:

Method	Scope	Safety	Time
CLI prune	All Docker data	High (if you read output)	~5 min
Docker Desktop GUI	Category by category	Very high (visual confirmation)	~10 min
Bytegone	13 categories incl. Docker	Moves to Trash by default	~10 sec

Reclaim disk space the safe way

Bytegone scans 13 reclaimable locations — including Docker images and volumes — and moves them to Trash with your confirmation. Never your work, never system files.

Download Bytegone

FAQ

Will pruning Docker break my running apps?

No — docker system prune never touches running containers or images they depend on. If you use -a, it only removes images not referenced by a running container. Stopped containers are removed, so start anything you want to keep before pruning.

Why does Docker Desktop use a single huge file?

Docker Desktop runs a lightweight Linux VM on macOS. All images, containers, and volumes live inside a sparse disk image (Docker.raw). Even if Docker reports 30 GB of data, macOS may show the file as larger because the sparse format does not automatically shrink. Compacting it requires resetting Docker Desktop to factory defaults.

How do I shrink the Docker.raw file itself?

After heavy pruning, the virtual disk may still appear large. The only reliable way to reclaim that space is:

Export any important images with docker save
Go to Docker Desktop → Troubleshoot → Clean / Purge data
Restart Docker Desktop

This rebuilds the virtual disk from scratch. It is drastic, so only do it after you have pruned aggressively and still need space.

Is Bytegone’s Docker cleanup the same as `docker system prune`?

Bytegone’s Docker cleanup is intentionally conservative. It targets dangling images, stopped containers, and unused volumes — the same categories as a careful manual prune — but it always lists candidates and asks for confirmation before acting. It never runs destructive commands automatically.