Docker Desktop
Docker Desktop uses an Electron-based interface on Windows and macOS, which creates Chromium disk cache files, V8 Code Cache bytecode, and GPUCache shader and rendering blobs to speed up the dashboard, settings screens, image lists, and embedded web views. Those caches can become stale after Docker Desktop updates, Chromium runtime changes, or graphics driver changes, leading to blank panes, sluggish startup, or broken rendering in the UI. Kudu removes only these disposable Electron cache files so Docker images, containers, volumes, settings, credentials, and Kubernetes data stay untouched.
Why clean Docker Desktop?
- Invalidated V8 Code Cache after a Docker Desktop update can make the app hang on a white or blank window during first launch until the bytecode is rebuilt
- Corrupted Chromium disk cache entries can leave the Images, Containers, or Extensions views stuck loading even though the Docker engine itself is running normally
- Stale GPUCache data from a graphics driver update can cause flickering panels, black sections, or missing buttons in the Electron interface
- Oversized cache directories slow Docker Desktop startup because the embedded Chromium runtime has to scan and rebuild cache indexes before the dashboard becomes responsive
- Broken cached frontend assets can make settings pages render incorrectly, with missing icons, unclickable controls, or layout glitches in the dashboard
- If Docker Desktop stores UI state in fragmented SQLite-backed cache files, page fragmentation can waste space and slow reads; VACUUM rewrites the database compactly without deleting rows
- Repeated cache corruption can produce a mismatch where the tray icon says Docker is ready but the main window keeps spinning or never finishes loading
Cache paths Kudu targets
Windows
%AppData%/Docker Desktop/cache |
%AppData%/Docker Desktop/Code Cache |
%AppData%/Docker Desktop/GPUCache |
macOS
~/Library/Caches/com.docker.docker |
Common questions about Docker Desktop
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.