How Do You Uninstall Docker Desktop on a Mac?

If you’re a Mac user who has been exploring containerization with Docker Desktop, you might find yourself needing to uninstall the application for various reasons—whether it’s to free up space, troubleshoot issues, or switch to an alternative solution. While Docker Desktop offers a powerful way to manage containers on macOS, removing it isn’t always as straightforward as dragging the app to the Trash. Understanding the proper steps ensures a clean uninstall without leftover files cluttering your system.

Uninstalling Docker Desktop on a Mac involves more than just deleting the main application. The software integrates with system components and stores configuration files that may persist if not removed correctly. This can affect system performance or cause conflicts if you plan to reinstall or replace Docker with another tool. Knowing what to look out for and how to approach the uninstallation process will save you time and prevent potential headaches.

In the following sections, we’ll explore the essential considerations and methods to fully uninstall Docker Desktop from your Mac. Whether you’re a casual user or a developer, this guide will prepare you to handle the removal process efficiently and confidently, ensuring your system stays clean and optimized.

Removing Docker Desktop Application and Associated Files

To completely uninstall Docker Desktop from your Mac, it is essential to remove not only the application itself but also all associated files and configurations that remain on your system. Simply dragging the Docker app to the Trash does not eliminate these residual files, which can consume disk space or cause conflicts if you reinstall Docker in the future.

Begin by quitting Docker Desktop if it is currently running. You can do this by right-clicking the Docker icon in the menu bar and selecting “Quit Docker Desktop.” Once the application is closed, proceed with the following steps:

Open the Applications folder and drag the `Docker.app` to the Trash.
Remove Docker’s support files, caches, and preferences stored within the user Library directory.
Delete Docker system files located in system-wide directories to ensure complete removal.

The common locations of these files include:

Location	Description
~/Library/Containers/com.docker.docker	Container data for Docker Desktop’s sandboxed environment
~/Library/Application Support/Docker Desktop	User-specific application support files and settings
~/Library/Group Containers/group.com.docker	Shared group container for Docker processes
/Library/PrivilegedHelperTools/com.docker.vmnetd	Helper tool for Docker networking
/Library/LaunchDaemons/com.docker.vmnetd.plist	Launch daemon to manage Docker’s networking services
~/.docker	User-specific Docker CLI configuration and credentials

To remove these files, open Terminal and execute the following commands carefully:

“`bash
rm -rf ~/Library/Containers/com.docker.docker
rm -rf ~/Library/Application\ Support/Docker\ Desktop
rm -rf ~/Library/Group\ Containers/group.com.docker
sudo rm -f /Library/PrivilegedHelperTools/com.docker.vmnetd
sudo rm -f /Library/LaunchDaemons/com.docker.vmnetd.plist
rm -rf ~/.docker
“`

Using `sudo` commands will prompt for your administrator password. Be cautious when running commands with elevated privileges to avoid unintended system changes.

Cleaning Up Docker-Related Virtual Networks and Containers

Docker Desktop on macOS creates virtual networks and runs lightweight containers within a virtualized environment. These networks and containers may persist even after uninstalling the application, so manual cleanup is necessary to free system resources and avoid conflicts.

Start by checking for any running or stopped containers and removing them. Since Docker Desktop is uninstalled, you may need to manually delete container data stored in the filesystem:

Containers and images are usually stored within the Docker virtual machine disk image.
If you have any custom virtual machines or volumes associated with Docker, remove their files.

For network interfaces created by Docker, use the `ifconfig` command to identify virtual network interfaces typically named `docker0`, `br-*`, or `veth*`. You can remove these interfaces with:

“`bash
sudo ifconfig docker0 down
sudo ifconfig docker0 destroy
“`

Repeat for any other Docker-related interfaces identified.

Using Terminal Commands for Complete Removal

For users comfortable with command-line operations, the Terminal offers precise control over the uninstallation process. Beyond deleting files, Docker Desktop includes services and daemons that need to be stopped and removed.

Execute the following commands to unload and delete Docker-related launch agents and daemons:

“`bash
launchctl unload ~/Library/LaunchAgents/com.docker.helper.plist
launchctl unload /Library/LaunchDaemons/com.docker.vmnetd.plist
rm -f ~/Library/LaunchAgents/com.docker.helper.plist
sudo rm -f /Library/LaunchDaemons/com.docker.vmnetd.plist
“`

This ensures that no background services continue running or restart after reboot.

Additionally, removing Docker CLI binaries, if installed separately, can be done by:

“`bash
sudo rm -f /usr/local/bin/docker
sudo rm -f /usr/local/bin/docker-compose
sudo rm -f /usr/local/bin/docker-machine
“`

Check if these binaries exist before attempting removal.

Verifying Complete Removal

After completing the uninstallation steps, verify that Docker Desktop and its components have been fully removed from your Mac. You can do this by:

Searching for Docker files and folders using Finder’s search feature, entering “Docker” as the keyword.
Running the following Terminal command to locate any remaining Docker files:

“`bash
find ~ /Library /usr/local -iname “*docker*” -print
“`

Checking active network interfaces to ensure no Docker virtual networks remain:

“`bash
ifconfig | grep docker
“`

Attempting to run the `docker` command in Terminal; it should return a “command not found” error if the CLI is fully removed.

If any Docker-related files, services, or interfaces persist, repeat the relevant deletion steps. This thorough approach guarantees a clean system state, ready for a fresh Docker installation or to free resources permanently.

Optional: Removing Docker Data Volumes and Images

Docker stores persistent data in volumes and images that can consume significant disk space. If you plan to uninstall Docker Desktop permanently, consider deleting these data stores manually.

Data volumes are usually stored inside the Docker VM or in the user’s home directory under `.docker` or `~/Library/Application Support/Docker Desktop`. Since Docker Desktop uses a virtualized environment on Mac (using HyperKit), the disk image file storing volumes and images is located at:

“`

Uninstalling Docker Desktop on Mac

To completely uninstall Docker Desktop from your Mac, you need to remove the application and its related files manually. This process ensures that no residual data remains on your system that could interfere with future installations or consume unnecessary disk space.

Step-by-Step Manual Uninstallation

Follow these steps carefully to remove Docker Desktop and its associated components:

Quit Docker Desktop:
- Ensure Docker Desktop is not running. Click the Docker icon in the menu bar, then select Quit Docker Desktop.
Remove the Docker Desktop Application:
- Open the Applications folder.
- Locate Docker.app, then drag it to the Trash or right-click and select Move to Trash.
Delete Docker Support Files and Directories:
- Open Finder, press Cmd + Shift + G to open the “Go to Folder” dialog.
- Enter the following paths one at a time and delete the Docker-related files and folders:

Path	Description
`~/Library/Application Support/Docker Desktop`	Contains application support files for Docker Desktop.
`~/Library/Containers/com.docker.docker`	Sandbox container data for Docker Desktop.
`~/Library/Group Containers/group.com.docker`	Shared container data and settings.
`~/Library/Preferences/com.docker.docker.plist`	User preferences and settings for Docker Desktop.
`/usr/local/bin/docker`	Docker CLI symbolic link.
`/usr/local/bin/docker-compose`	Docker Compose CLI symbolic link.
`/usr/local/bin/docker-credential-desktop`	Docker credential helper binary.

To delete these files and directories, you can use the Finder or run commands in the Terminal (prefixed with rm -rf for directories and rm for files).

Using Terminal Commands for Cleanup

For users comfortable with the Terminal, executing the following commands will automate the removal of Docker Desktop files and symlinks. Open Terminal and run:

osascript -e 'quit app "Docker"'
rm -rf ~/Library/Application\ Support/Docker\ Desktop
rm -rf ~/Library/Containers/com.docker.docker
rm -rf ~/Library/Group\ Containers/group.com.docker
rm -f ~/Library/Preferences/com.docker.docker.plist
rm -f /usr/local/bin/docker
rm -f /usr/local/bin/docker-compose
rm -f /usr/local/bin/docker-credential-desktop

Note: Some commands may require sudo privileges depending on your system’s permissions.

Removing Docker Images, Containers, and Volumes

Uninstalling Docker Desktop does not automatically remove Docker images, containers, or volumes stored on your Mac. To clear these artifacts, perform the following before uninstalling:

Open Terminal.
Stop all running containers:

docker stop $(docker ps -aq)

Remove all containers:

docker rm $(docker ps -aq)

Remove all images:

docker rmi $(docker images -q)

Remove all volumes:

docker volume rm $(docker volume ls -q)

This cleanup helps free up disk space and ensures no leftover Docker data remains on your machine.

Expert Guidance on How To Uninstall Docker Desktop Mac

Jessica Lin (Senior DevOps Engineer, CloudTech Solutions). When uninstalling Docker Desktop on a Mac, it is crucial to first stop all running containers and remove any associated volumes to prevent residual data. Using the official Docker uninstall script or manually deleting the application from the Applications folder followed by clearing configuration files in the ~/Library directory ensures a thorough removal.

Dr. Michael Chen (Mac Systems Administrator, TechWave Consulting). The recommended approach to uninstall Docker Desktop on macOS involves quitting the application completely, then dragging the Docker app to the Trash. After that, removing related files from ~/Library/Containers/com.docker.docker and ~/Library/Application Support/Docker Desktop is essential to avoid leftover components that could interfere with future installations.

Emily Carter (Software Development Manager, NextGen Cloud Infrastructure). For a clean uninstall of Docker Desktop on a Mac, I advise users to leverage the built-in uninstall feature found within the Docker Desktop preferences if available. Additionally, running terminal commands to purge Docker-related system files and caches helps maintain system integrity and prevents conflicts with other containerization tools.

Frequently Asked Questions (FAQs)

How do I completely uninstall Docker Desktop on a Mac?
To completely uninstall Docker Desktop on a Mac, first quit the application. Then, drag the Docker app from the Applications folder to the Trash. Finally, remove related files by deleting `~/Library/Containers/com.docker.docker`, `~/Library/Application Support/Docker Desktop`, and `~/Library/Group Containers/group.com.docker`.

Will uninstalling Docker Desktop remove all my containers and images?
Yes, uninstalling Docker Desktop removes all local containers, images, volumes, and settings stored on your Mac unless you back them up beforehand.

Do I need to stop Docker services before uninstalling Docker Desktop on Mac?
Yes, it is recommended to quit Docker Desktop completely to stop all Docker-related services before uninstalling to avoid file access issues.

How can I remove Docker command-line tools after uninstalling Docker Desktop?
Docker CLI tools are bundled with Docker Desktop on Mac. Uninstalling the app removes these tools. If you installed Docker CLI separately, remove them manually from `/usr/local/bin` or your custom installation path.

Is there a terminal command to uninstall Docker Desktop on Mac?
There is no official single terminal command to uninstall Docker Desktop on Mac. However, you can manually remove the app and its support files using `rm -rf` commands in Terminal, but caution is advised to avoid deleting unintended files.

Will uninstalling Docker Desktop affect my system’s network settings?
Uninstalling Docker Desktop removes Docker-specific network interfaces and configurations. It does not affect your Mac’s general network settings or other applications.
Uninstalling Docker Desktop on a Mac involves a few straightforward steps to ensure complete removal of the application and its associated files. The process typically includes quitting Docker Desktop, deleting the application from the Applications folder, and removing related system files such as Docker containers, images, volumes, and configuration data stored in hidden directories. Utilizing terminal commands can help in thoroughly cleaning up residual files that are not removed through the graphical interface alone.

It is important to back up any critical Docker data before proceeding with the uninstallation, especially if you have containers or images that you may want to preserve. Additionally, understanding the locations of Docker’s supporting files on macOS, such as those in the ~/Library and /usr/local directories, can help in performing a comprehensive cleanup. This ensures that no unnecessary files remain that could consume disk space or interfere with future Docker installations.

Overall, following a systematic approach to uninstall Docker Desktop on Mac not only frees up system resources but also prepares the environment for a clean reinstallation if needed. Adhering to best practices during the uninstallation process minimizes the risk of configuration conflicts and maintains the integrity of your macOS system. For users seeking to reinstall or switch to alternative container solutions, a complete uninstall is a crucial first

Author Profile

Barbara Hernandez: Barbara Hernandez is the brain behind A Girl Among Geeks a coding blog born from stubborn bugs, midnight learning, and a refusal to quit. With zero formal training and a browser full of error messages, she taught herself everything from loops to Linux. Her mission? Make tech less intimidating, one real answer at a time.

Barbara writes for the self-taught, the stuck, and the silently frustrated offering code clarity without the condescension. What started as her personal survival guide is now a go-to space for learners who just want to understand what the docs forgot to mention.