Rancher Desktop diffdisk Taking Too Much Space On Mac?

Rancher Desktop and Lima can hide large storage under Application Support. The safe path is to measure diffdisk, logs, images, build cache, and volumes separately before deleting anything that may contain local databases.

Check The Real Size First

`diffdisk` is often sparse, so Finder or `ls -lh` can be misleading. Compare apparent size with allocated size before making a cleanup decision.

rd="$HOME/Library/Application Support/rancher-desktop/lima"
du -sh "$rd" 2>/dev/null
find "$rd" -maxdepth 4 -type f -size +1G -print0 2>/dev/null | xargs -0 du -h 2>/dev/null | sort -hr | head -30
ls -lh "$rd/0/diffdisk" 2>/dev/null
du -h "$rd/0/diffdisk" 2>/dev/null

Usually Lower Risk

• Runaway Rancher Desktop or Lima log files after Rancher Desktop is fully stopped.
• Unused Docker images, stopped containers, and build cache shown by `docker system df`.
• Temporary files under Rancher Desktop cache paths that are not active volumes.

Review First

• `diffdisk`, because it may contain images, layers, and data still needed by the VM.
• Docker volumes, especially local databases, queues, object stores, or development fixtures.
• Factory reset, because it can recover space but may wipe local container state.

Safe Triage Order

1. Quit Rancher Desktop and confirm the VM processes are stopped.
2. Measure large files with `du`, not just Finder or `ls`.
3. Run `docker system df -v` and identify whether reclaimable space is images/cache or volumes.
4. Export or back up any local database volumes before pruning.
5. Delete only runaway logs first, then restart Rancher Desktop and remeasure.