How to Clean Docker Desktop BuildKit Container Cache & Dangling Images
Location & Quick Verdict
%LocalAppData%\Docker\wsl\data and %UserProfile%\.docker\buildx
Docker Desktop accumulates gigabytes of cached intermediate container layers, multi-arch buildx builders, and dangling image blobs on your C: drive.
How Windows Manages Docker Desktop BuildKit Container Cache & Dangling Images on NTFS & NVMe Drives
Windows 10 and Windows 11 maintain hidden system directories and root-level allocation files at %LocalAppData%\Docker\wsl\data and %UserProfile%\.docker\buildx to handle shell thumbnail databases, prefetcher launch traces, hibernation power states, and user-profile scratch storage. Because many of these paths are marked with +H (Hidden) or +S (System) attributes or guarded by SYSTEM ACL permissions, standard folder size scans often miss them entirely.
Over time, orphaned temporary files, stale Explorer DataCache_* buckets, and uncompacted virtual storage allocations inside %LocalAppData%\Docker\wsl\data and %UserProfile%\.docker\buildx lock up 12.0 GB – 75.0 GB of primary C: drive space. Cleaning Docker Desktop BuildKit Container Cache & Dangling Images using the proper administrative method restores drive headroom safely.
# Inspect current disk footprint of Docker Desktop BuildKit Container Cache & Dangling Images (Read-Only)
$target = "$env:LOCALAPPDATA\Docker\wsl\data"
Get-ChildItem -Path $target -Recurse -Force -ErrorAction SilentlyContinue |
Measure-Object -Property Length -Sum |
Select-Object Count, @{Name="SizeGB";Expression={[math]::Round($_.Sum / 1GB, 2)}}
Manual Cleaning Instructions
- 1 Open Windows Terminal or PowerShell.
- 2 Run 'docker builder prune -a' to clear all cached BuildKit layers.
- 3 Run 'docker image prune -a' to remove dangling, untagged Docker images.
Note: If Windows alerts that a file is in use or locked by a background process, close the associated task in Task Manager before deleting, or use SWEEPR Cleaner to release locked handles safely.
Sub-Folders & Cache Locations Breakdown for Docker Desktop BuildKit Container Cache & Dangling Images
Modern Windows applications and system services split their disk footprint across multiple sub-directories (`Cache_Data`, `Service Worker\CacheStorage`, `Code Cache`, `GPUCache`, and `Crashpad\reports`). Review which sub-folders inside Docker Desktop BuildKit Container Cache & Dangling Images are safe to purge and which files remain protected:
| Sub-Folder / Cache Location | Storage Role | Typical Footprint | Deletion Safety |
|---|---|---|---|
| %LocalAppData%\Docker\wsl\data | Primary System Scratch, Thumbnail/Icon DB or Virtual Allocation | 12.0 GB – 75.0 GB | 🟢 100% Safe (Unlocked Files) |
| %LocalAppData%\Temp & C:\Windows\Temp | Orphaned Installer Extraction & Session Scratch Files | 1.5 GB – 18.0 GB | 🟢 100% Safe |
| %LocalAppData%\Microsoft\Windows\Explorer (thumbcache_*.db) | Cached File Explorer Image & Video Thumbnail Databases | 250 MB – 3.0 GB | 🟢 100% Safe (Rebuilds Automatically) |
| User Documents, Desktop & Registry Hives | Personal Files, Boot Configuration & System Certificates | Protected | 🔒 Protected — Never Touched |
Frequently Asked Questions
Is it safe to delete Docker Desktop BuildKit Container Cache & Dangling Images?
Yes, 100% safe. Safely cleans orphaned Docker build caches and unused container layers without deleting running containers or volumes.
How much storage space will cleaning Docker Desktop BuildKit Container Cache & Dangling Images free up?
Users typically reclaim 12.0 GB – 75.0 GB on Windows 10 and Windows 11 systems depending on update frequency and active cache retention in %LocalAppData%\Docker\wsl\data and %UserProfile%\.docker\buildx.
Why does Windows say some files in Docker Desktop BuildKit Container Cache & Dangling Images are "In Use" when I try to delete them?
Active background processes (such as explorer.exe, svchost.exe, or running desktop apps) hold open file handles to current session scratch files. Skipping locked files—or letting SWEEPR Cleaner clean unlocked items automatically—is normal and completely safe.
Where is Docker Desktop BuildKit Container Cache & Dangling Images located on Windows 10 and Windows 11?
It is stored at %LocalAppData%\Docker\wsl\data and %UserProfile%\.docker\buildx. You can paste that path directly into the Windows Run dialog (Win + R) or File Explorer address bar to inspect it.
Manual File Explorer vs. 1-Click SWEEPR Cleanup
| Feature | Manual Deletion | SWEEPR Cleaner |
|---|---|---|
| Locked File Handling | Fails on locked processes | Safe background release |
| Accidental Deletion Risk | Moderate (easy to delete wrong folder) | Zero (strict rules & hashes) |
| Safety Undo Rollback | None (Shift+Del is permanent) | 7-Day Automatic Rollback |
| Time Required | 10–20 minutes per app | < 60 seconds across 40+ areas |
Related Windows Cleanup Guides & Hidden Space Hogs
Clean Docker Desktop BuildKit Container Cache & Dangling Images Automatically
SWEEPR Cleaner safely clears Docker Desktop BuildKit Container Cache & Dangling Images along with 40+ other hidden app folders and leftover files in one click—covering up to 5 devices (Windows, Mac, Android & iOS) with a 7-day undo safety net.