How to uninstall Docker Desktop on a Mac

Back up before uninstalling

Keep the source, Compose files, environment configuration and a record of how to recreate the services. Preserve locally built images you cannot obtain again. Back up named-volume data, bind-mounted host files and database contents using the appropriate application procedure before removal.

Docker’s backup documentation distinguishes image backups from volume backups. Saving or committing an image does not include data in an attached volume. Treat a database dump or a volume backup as its own task, and verify the result before destroying the local engine.

If Docker Desktop cannot start, Docker documents backing up the VM disk with the app fully stopped. The default Mac path is ~/Library/Containers/com.docker.docker/Data/vms/0/data/Docker.raw. A custom disk-image location takes precedence. Copy the confirmed disk file to separate safe storage; do not move or delete it as an experiment.

For a work or school development environment, ask IT before removal. They may manage licenses, networking, credentials and shared project requirements. The following steps describe your authorized local installation, not an organization’s remote Docker engine.

Use Docker Desktop’s uninstaller

1. Complete the backup and stop work that needs the local containers.
2. Open Docker Desktop.
3. In the Dashboard, choose the Troubleshoot icon at the top right.
4. Choose Uninstall, read the consequences, then confirm Uninstall again.
5. After the uninstaller finishes, move the Docker application to the macOS Trash.

This is the vendor’s documented Mac GUI route, checked 23 October 2026. Removing only the app bundle first skips the documented uninstaller. We did not execute either removal method while writing this guide.

Docker also publishes a command-line uninstaller inside its app bundle. Use the official troubleshooting route if the Dashboard cannot open, particularly if protected-container access produces an error. Do not substitute a command that deletes every folder with docker in its name.

Why Docker.raw looks so large

Docker Desktop keeps Linux containers and images in a disk-image file. The file’s maximum logical size and the space currently allocated on the Mac are different quantities. A large number reported by one file browser does not necessarily mean all that space is physically occupied.

Check Docker Desktop › Settings › Resources › Advanced for the image location, maximum size and actual use. Docker documents that other tools can show the maximum instead of the amount consumed. There is no single size that every installation “should” have.

If you want to move the image, use Docker’s Disk image location control. Docker warns against moving the active file directly in Finder because the app can lose track of it. A smaller size limit is also not a harmless shrink operation: its documentation says reducing that limit deletes the current disk image and loses containers and images.

The System Data guide explains why broad macOS categories cannot tell you which developer files are dispensable. Do not delete Docker.raw from a disk map while you still need the local environment.

If you only want to reclaim space

Start with these read-only Docker commands against the local engine you intend to inspect:

docker system df -v
docker image ls
docker container ls -a

They list usage, images and containers; they do not prune data. Docker commands follow the current context, which may point somewhere remote. Confirm the target before any cleanup so that you do not remove a different engine’s objects.

Review unused objects in the Dashboard or follow Docker’s documented prune procedures. An unused object can still contain something valuable: a stopped container can hold unexported work, and a detached volume can hold a database you plan to reconnect.

The basic docker system prune removes stopped containers, unused networks, dangling images and unused build cache. It does not prune volumes by default. Adding broader flags changes the scope; this guide does not recommend them as routine maintenance. Volume removal is a separate decision requiring its own backup.

Do not promise an exact reclaimed amount from a list of logical object sizes. Docker’s storage accounting and the host disk image need time to reflect the change. Check actual host space after the selected operation has completed.

Review leftovers conservatively

Docker’s removal documentation identifies ~/Library/Group Containers/group.com.docker and ~/.docker as possible residual locations. The user container ~/Library/Containers/com.docker.docker can also remain when protected metadata prevents its removal.

Inspect those exact locations only after uninstalling and preserving needed data. Keep ~/.docker if another Docker CLI setup still needs its contexts, configuration or credentials. A generic app cleaner cannot infer which remaining development tools depend on that configuration.

A protected metadata error does not justify turning off macOS protection or deleting shared helpers by hand. Docker documents a case where the uninstall succeeded despite a container metadata error. Match the exact message to its current advice rather than repeatedly rerunning destructive operations.

App removal and billing

Uninstalling the local app does not cancel a Docker subscription or delete your Docker account. Check the account or organization that owns the plan if you intend to end service. An organization’s administrator should handle its seats and billing; the local uninstaller is a separate tool.

Where Tend fits

Tend’s free Space Map can show eligible storage inside your home folder, including a large Docker data location when accessible. It cannot decide whether a Docker volume is disposable. Use Docker’s backup and removal controls rather than treating its disk image as a cache.

Tend Pro moves reviewed app and user-Library support files to the Trash, but it does not replace Docker’s engine-aware uninstall or prune. For other developer storage, see Xcode cleanup and cache cleanup.

Questions

Related guides

Sources

• Docker, Docker Desktop uninstall and backup and restore.
• Docker, Mac disk-image storage and prune scope and warnings.
• Docker, contexts and target engines.
• Docker was unavailable in the local command check. All Docker commands here are reference instructions; no Docker data was changed.

Sources checked 23 October 2026. Spotted something out of date? Tell us and we'll fix it.