Docker Desktop Disk Image Location Hangs On External Drive

When Docker Desktop gets stuck on Apply & restart after moving Disk Image Location to an external volume, capture the disk-image state before reinstalling, symlinking, or resetting Docker data.

Why Apply & Restart Hangs

The setting touches more than a path string. Docker Desktop has to stop the VM, move or attach the disk image, restart backend services, and keep Docker storage metadata consistent. A hang can be caused by the external volume, permissions, sparse file behavior, backend service state, or a disk image already near its limit.

Capture Evidence First

Before uninstalling, symlinking, shrinking the disk limit, or moving the folder again, record the current state.

df -h
diskutil info "/Volumes/YOUR_EXTERNAL_VOLUME"
du -sh "$HOME/Library/Containers/com.docker.docker/Data" 2>/dev/null
ls -lh "$HOME/Library/Containers/com.docker.docker/Data/vms/0/data/Docker.raw" 2>/dev/null
docker system df -v 2>/dev/null || true

Review These Buckets

• External volume format: APFS is usually safer for Docker Desktop disk images than exFAT or network-mounted storage.
• Host free space: both the original Mac volume and target external volume need enough free space during the move.
• Docker.raw size: apparent size and allocated size can differ, especially when sparse files are involved.
• Named volumes: these often hold local databases and should not be blindly pruned.
• Backend state: if Docker CLI or diagnostics hang, treat that as evidence, not as a signal to delete everything.

Safer Recovery Order

1. Quit Docker Desktop and confirm backend processes are stopped.
2. Record disk and Docker storage evidence from the commands above.
3. If Docker still answers, prune build cache and unused images before touching volumes.
4. Use Docker Desktop settings for path changes where possible; manual symlinks deserve extra caution and rollback notes.
5. Use a full reset only when you are ready to lose local Docker images, containers, and volumes.