How to Uninstall Docker on Mac Completely

If you want to uninstall Docker on a Mac, pause before clicking the button: Docker says the uninstall destroys local containers, images, volumes, and other Docker-related data. Back up anything you need, run Docker Desktop's own uninstaller, then decide separately whether its remaining CLI settings should stay.

Your source code and bind-mounted folders normally live outside Docker Desktop, but named volumes and images can disappear with its virtual disk. That boundary matters more than finding the longest possible list of Library folders.

Quick Answer: Uninstall Docker Desktop in the Right Order

1. Inventory local data with docker system df -v while Docker Desktop still works.
2. Back up wanted images, volumes, and container definitions. Confirm where bind-mounted folders live on the Mac.
3. Open Docker Desktop, choose the Troubleshoot icon, select Uninstall, and confirm.
4. If the app will not open, run Docker's official CLI uninstaller:

/Applications/Docker.app/Contents/MacOS/uninstall

5. Move Docker.app to Trash after the uninstaller finishes.
6. Review residual settings before removing them. In particular, ~/.docker may still be useful to another Docker-compatible runtime or remote context.
7. Verify the result before emptying Trash or deleting backups.

Docker's current uninstall guide is explicit about the data loss. Moving only Docker.app to Trash is not the supported complete workflow.

Step 1: Decide Which Docker Data Must Survive

Separate Docker-managed data from ordinary files on your Mac. They do not all follow the application into Trash.

A named volume and a bind mount can both hold application data, but they have different owners. A bind mount points at a host path you chose. Uninstalling Docker Desktop should not delete that source folder. A named volume lives in Docker-managed storage and needs its own export or migration plan.

Tip: If a database matters, test its backup with the database's own restore procedure. An old container that happens to start is not a reliable backup strategy.

Step 2: Inventory Containers, Images, Volumes, and Disk Use

Run read-only inventory commands before changing anything. With Docker Desktop running, open Terminal and start with:

docker system df -v

Docker's Mac FAQ recommends this command for detailed local space use. Then list each object type:

docker container ls -a
docker image ls
docker volume ls

Record the names of anything you intend to preserve. For containers created with Compose, keep the current compose.yaml, environment-file strategy, secrets plan, and any build files needed to recreate them. Do not copy secrets into the article checklist or an unencrypted notes file.

If your only goal is to recover space, check Docker Desktop's Settings > Resources > Advanced page first. Docker documents that its Linux containers and images live in one large disk-image file on Mac, normally Docker.raw. Removing unused Docker objects may solve the storage problem without uninstalling the application.

Step 3: Back Up What You Cannot Recreate

Use Docker-aware backups while the engine is healthy. Docker's backup and restore guide separates images, container recreation, and volume data for a reason.

For an image that is not already available from a registry or reproducible build, save it to a tar archive:

docker image save -o my-image-backup.tar image-name:tag

Alternatively, push it to a registry you control. Keep Compose files or the original docker run options so you can recreate containers after reinstalling. docker container commit can turn a container's writable layer into an image, but it does not include data stored in mounted volumes.

Back up named volumes using the procedure recommended for that workload. Database-native dumps are often easier to verify than a raw filesystem copy. Bind-mounted data should be backed up from its source folder on the Mac.

If Docker Desktop will not start, Docker documents a last-resort whole-VM copy. Fully stop Docker Desktop, then copy:

~/Library/Containers/com.docker.docker/Data/vms/0/data/Docker.raw

That file can be very large. Treat it as recovery material for a compatible Docker Desktop reinstall, not as a browsable archive of individual volumes. Keep the original copy unchanged until the recovery has been tested.

Tip: Check the destination's free space before copying Docker.raw. Finder may show a large maximum size that differs from the disk space actually consumed, so leave comfortable headroom.

Step 4: Uninstall Docker Desktop from Its Dashboard

Use Docker's own uninstaller when the app opens. The current Mac path in Docker's documentation is:

1. Open Docker Desktop.
2. Select the Troubleshoot icon in the top-right of the Dashboard.
3. Select Uninstall.
4. Read the data-loss warning and confirm Uninstall again.
5. When it finishes, move Docker.app from Applications to Trash.

Before starting, quit editors or terminal jobs that are actively using containers. Save work and stop any development database cleanly. The uninstaller is supposed to remove Docker Desktop's managed data; an active workload does not make that data safer.

Apple's current Mac app removal guidance says to prefer a third-party app's included uninstaller because it can remove login items, extensions, and data stored outside the app bundle. Docker Desktop is exactly the kind of app where that advice matters.

I would leave Docker.app in Trash until the verification step is complete. Trash is a recovery boundary for the app bundle, though it cannot restore Docker data that the uninstaller already destroyed.

Step 5: Use Docker's CLI Uninstaller If the App Will Not Open

The command-line path is useful for a broken installation. Run Docker's documented uninstaller as a standalone command:

/Applications/Docker.app/Contents/MacOS/uninstall

Follow its prompts, then move Docker.app to Trash. Do not wrap this command in a script that also removes every path containing the word “docker.” You need to see whether the supported uninstall itself succeeded before making optional cleanup decisions.

Docker documents one confusing macOS result: the uninstaller can report operation not permitted for .com.apple.containermanagerd.metadata.plist or its parent ~/Library/Containers/com.docker.docker directory. Docker says that error can be ignored when Docker Desktop otherwise uninstalled successfully. If you later remove the remaining container directory manually, the terminal application may need System Settings > Privacy & Security > Full Disk Access.

Grant that permission only to the terminal you are using, retry the exact documented folder, and remove the permission afterward if you do not normally need it. Do not respond to one protected metadata file by disabling broader macOS security controls.

Step 6: Review Docker Desktop's Residual Files

Residual configuration is optional cleanup, not the first uninstall step. Docker currently names these possible leftovers on Mac:

~/Library/Group Containers/group.com.docker
~/.docker

Use Finder > Go > Go to Folder to inspect each path. Move only the Docker Desktop data you have decided not to keep, then verify before emptying Trash.

The two locations deserve different decisions:

• group.com.docker contains Docker Desktop group-container settings and app data.
• .docker can contain CLI configuration, contexts, credential-store settings, and preferences used to reach remote Docker engines or another local runtime.

If you are switching from Docker Desktop to another Docker-compatible setup, keep .docker until you know which contexts and credentials the replacement needs. If you want a genuinely fresh Docker Desktop reinstall, removing it may be appropriate after you back up any required configuration.

Tip: “Leftover” does not mean “worth deleting.” A small config file may save more time than the storage it consumes.

Step 7: Keep Other Runtimes and Project Files Separate

Docker Desktop is not every tool that happens to use the docker command. A Mac can also have command-line packages, Colima or Lima virtual machines, Kubernetes configuration, remote contexts, and development files installed through separate workflows.

Do not remove these automatically:

• source repositories, Compose files, Dockerfiles, or environment templates;
• bind-mounted project and database folders on the Mac;
• Homebrew packages installed independently of Docker Desktop;
• Colima, Lima, OrbStack, Podman, or another runtime's data;
• ~/.kube configuration;
• images stored in Docker Hub or another remote registry.

Uninstall each separate tool with its own current documentation and package manager. A “complete Docker cleanup” should not become an unreviewed developer-environment reset.

Step 8: Verify Docker Desktop Is Gone

Check the outcome against your goal, not against a broad filename search.

1. Confirm Docker.app is no longer in Applications.
2. Confirm Docker Desktop no longer starts from Spotlight or Login Items.
3. Open System Settings > General > Storage and allow macOS time to recalculate.
4. Check that source repositories and bind-mounted host folders still exist.
5. If you kept another runtime or remote context, verify it through that tool's own documentation.
6. Keep backups until the required image, volume, or database has been restored and tested.

The docker command may still exist if it was installed separately or another runtime supplies it. That does not prove Docker Desktop remains installed. Identify the owner before deleting a binary or package.

The Mac storage guide helps compare space before and after macOS finishes recalculating. For broader cleanup, use the disk-space guide rather than continuing to search for Docker-named files.

Review Remaining App Files with Sensei

Docker's uninstaller owns the Docker-specific removal; Sensei can help with the ordinary Mac-app cleanup around it. Sensei's current Uninstaller scans applications and associated local files. As of August 2026, Sensei 2.1.2 requires macOS 14 or later.

Use Sensei before removal only after the Docker backup decision is complete, or afterward to review remaining local app files. It does not export Docker images, understand which named volumes contain important data, or replace Docker's own uninstaller.

That division keeps the workflow honest: Docker handles its runtime and local objects; Sensei helps review Mac application files you still intend to remove.

Remove the Runtime Without Erasing the Wrong Work

A complete Docker Desktop uninstall starts with preservation, not deletion. Inventory local objects, back up the volumes and images you cannot rebuild, use Docker's supported uninstaller, and review .docker separately from the app's VM data.

Once Docker's part is finished, Sensei can help review ordinary app leftovers without pretending it knows which developer data matters to you.

Optimize Your Mac with Sensei

Monitor performance, clean storage, and manage Mac maintenance in one native app, with a full 7-day trial before you decide.

Download Free TrialView All Plans

Related Guides

• How to Uninstall Apps on Mac Completely
• How to Check Mac Storage
• How to Free Up Disk Space on Mac
• How to Manage Startup Programs on Mac