Fixing Docker Desktop Not Starting on macOS Sequoia: A Complete Guide

The Problem

Since the release of macOS Sequoia (macOS 15), many Docker users have encountered a frustrating issue: Docker Desktop simply refuses to start properly. If you’re experiencing this problem, you might notice:

• Docker processes appear in Activity Monitor, but no UI launches
• Running docker version in the terminal results in an error message asking if Docker Desktop is running
• The error message: “Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?”

This issue has been reported by users across different Mac models, including those with Apple Silicon chips like the M2, and affects even the latest Docker Desktop versions.

Root Causes

The primary causes appear to be:

1. DNS resolution issues stemming from macOS Sequoia firewall bugs
2. Possible conflicts with previous Docker installations
3. Permission issues with certain Docker-related files
4. System Integrity Protection (SIP) interfering with Docker operations

The Solution: Complete Docker Reset

After analyzing numerous user reports and successful fixes, the most reliable solution is a complete removal of Docker and all its components, followed by a fresh installation. Here’s a step-by-step guide to fix the problem:

Step 1: Stop Docker Application

First, ensure Docker is completely stopped:

• Quit Docker Desktop from the menu bar if possible
• Check Activity Monitor to ensure all Docker processes are terminated
• If necessary, force quit any stubborn Docker processes

Step 2: Uninstall Docker

Run the official uninstaller:

1. In Finder, navigate to Applications
2. Right-click on Docker.app
3. Select “Show Package Contents”
4. Navigate to Contents → MacOS
5. Run the “Uninstall” application

Step 3: Manually Remove Remaining Docker Files

This is the crucial step that resolves most issues. Run the following commands in Terminal to completely remove all Docker-related files and directories from your system:

sudo rm -Rf /Applications/Docker.app
sudo rm -f /usr/local/bin/docker
sudo rm -f /usr/local/bin/docker-machine
sudo rm -f /usr/local/bin/com.docker.cli
sudo rm -f /usr/local/bin/docker-compose
sudo rm -f /usr/local/bin/docker-compose-v1
sudo rm -f /usr/local/bin/docker-credential-desktop
sudo rm -f /usr/local/bin/docker-credential-ecr-login
sudo rm -f /usr/local/bin/docker-credential-osxkeychain
sudo rm -f /usr/local/bin/hub-tool
sudo rm -f /usr/local/bin/hyperkit
sudo rm -f /usr/local/bin/kubectl.docker
sudo rm -f /usr/local/bin/vpnkit
sudo rm -Rf ~/.docker
sudo rm -Rf ~/Library/Containers/com.docker.docker
sudo rm -Rf ~/Library/Application\ Support/Docker\ Desktop
sudo rm -Rf ~/Library/Group\ Containers/group.com.docker
sudo rm -f ~/Library/HTTPStorages/com.docker.docker.binarycookies
sudo rm -f /Library/PrivilegedHelperTools/com.docker.vmnetd
sudo rm -f /Library/LaunchDaemons/com.docker.vmnetd.plist
sudo rm -Rf ~/Library/Logs/Docker\ Desktop
sudo rm -Rf /usr/local/lib/docker
sudo rm -f ~/Library/Preferences/com.docker.docker.plist
sudo rm -Rf ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState
sudo rm -f ~/Library/Preferences/com.electron.docker-frontend.plist

Warning: This will completely remove Docker and all associated data, including images, containers, volumes, and settings. Make sure to back up any important data before proceeding.

Step 4: Handle Permission Issues (If Encountered)

If you encounter “Operation not permitted” errors during the removal process, particularly with files like:

rm /Users/username/Library/Containers/com.docker.docker/.com.apple.containermanagerd.metadata.plist: Operation not permitted

You have two options:

1. Disable System Integrity Protection (SIP) temporarily:
   • This is a more advanced solution and should be used with caution
   • Reboot into Recovery Mode (hold Command+R during startup)
   • Open Terminal and run csrutil disable
   • Reboot normally, remove the files, then re-enable SIP in Recovery Mode with csrutil enable
2. Skip those specific files and continue with the rest of the removal process. In many cases, a fresh install will overwrite them properly.

Step 5: Clean Up Homebrew Installations (If Applicable)

If you’ve used Homebrew to install Docker-related packages, clean those up as well:

bashCopybrew remove docker-completion docker-credential-helper docker

Step 6: Reboot Your Mac

A system reboot is highly recommended before reinstalling Docker:

sudo reboot

Step 7: Reinstall Docker Desktop

1. Download the latest version of Docker Desktop for Mac from the official Docker website
2. Make sure to select the appropriate version for your Mac’s processor (Intel or Apple Silicon)
3. Run the installer and follow the instructions to complete the installation

Additional Troubleshooting Tips

If you’re still experiencing issues after following the above steps, consider these additional measures:

1. Temporarily disable your Mac’s firewall during installation
2. Check your network settings for any DNS resolver issues
3. Update macOS to the latest version (some users reported fixes in macOS 15.2 and 15.3)
4. Contact Docker support with your Diagnostics ID if problems persist

Confirmed Working Configurations

This solution has been confirmed to work on:

• macOS Sequoia 15.0.1 (24A348)
• macOS Sequoia 15.2 (24C101)
• macOS Sequoia 15.3.1

Final Thoughts

The Docker Desktop startup issue on macOS Sequoia appears to be related to how the new version of macOS handles certain system files and permissions. While a complete removal and reinstallation is not the most elegant solution, it has proven to be the most effective for the vast majority of users experiencing this problem.

Docker will likely release updates to address these compatibility issues more gracefully in future versions, but for now, this reset approach provides a reliable way to get Docker Desktop working again on your Mac.

Have you encountered this issue or found another solution? Share your experience in the comments below!