Docker Data & overlay2 Folder (var/lib/docker)

Bottom Line: You can safely clean up overlay2 and Docker data using official Docker prune commands (docker system prune). Do NOT manually delete the overlay2 directory in your file manager, as doing so will corrupt your Docker daemon storage index.

What is the Docker overlay2 Folder?

Located at /var/lib/docker/overlay2 on Linux (or inside Docker Desktop’s virtual disk on Windows/macOS), overlay2 is the storage driver directory used by Docker.

Every time you pull a Docker image, build a container, or run docker build, Docker creates multiple read-only image layers and writable container layers inside overlay2. Even after you stop or delete a container, Docker keeps unused images, dangling build caches, and volumes stored in overlay2.

Over months of development, overlay2 can silently grow to 30 GB, 50 GB, or 100 GB+.

Can You Delete overlay2?

• Manually deleting /var/lib/docker/overlay2: ❌ Never do this. It breaks Docker, preventing containers from starting until you re-install Docker completely.
• Cleaning via docker system prune: ✅ 100% safe. It removes stopped containers, dangling images, unused build caches, and unattached networks.

How to Safely Clean Up Docker overlay2

Always use official Docker CLI commands to clean out unused data.

Method 1: Remove All Unused Docker Data (Recommended)

Open your terminal or command prompt and run:

docker system prune -a --volumes

What this command does:

• Removes all stopped containers.
• Removes all unused networks.
• Removes all dangling and unused images (-a).
• Removes all unused build cache and volumes (--volumes).

Method 2: Clean Only Build Cache (If You Want to Keep Images)

If you want to keep your downloaded images but delete gigabytes of leftover build layers:

docker builder prune -a

What Happens After You Clean It?

• You immediately recover 10 GB to 80 GB+ of SSD space.
• Docker continues to work cleanly.
• Active, running containers are unaffected.

Related Guides

• Learn about shrinking [WSL2 virtual disk (ext4.vhdx)].
• How to clean up node_modules folders.
• Check if you can delete npm cache.