Docker will not run on MacOS

[chriscardillo]

Description

Been following #7527

Upgraded my MacOS to Sequoia 15.3 (Intel chip)

Uninstalled Docker (deleted Docker from the Applications Folder) and reinstalled the latest available version of Docker for Intel.

The output of ./check.sh /Applications/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd for me (as recommend here) is:

unable to load certificate
140704606341888:error:09FFF06C:PEM routines:CRYPTO_internal:no start line:/AppleInternal/Library/BuildRoots/d187755d-b9a3-11ef-83e5-aabfac210453/Library/Caches/com.apple.xbs/Sources/libressl/libressl-3.3/crypto/pem/pem_lib.c:694:Expecting: TRUSTED CERTIFICATE

Reproduce

Freshly install Docker for intel chip on MacOS Sequoia 15.3.

Double-click the Docker icon in your Applications folder.

Expect Docker to open but it never does.

Expected behavior

Running docker ps will list containers.

docker version

Client:
 Version:           27.4.0
 API version:       1.47
 Go version:        go1.22.10
 Git commit:        bde2b89
 Built:             Sat Dec  7 10:35:43 2024
 OS/Arch:           darwin/amd64
 Context:           desktop-linux
Cannot connect to the Docker daemon at unix:///Users/chriscardillo/.docker/run/docker.sock. Is the docker daemon running?

docker info

Client:
 Version:    27.4.0
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.19.2-desktop.1
    Path:     /Users/chriscardillo/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.31.0-desktop.2
    Path:     /Users/chriscardillo/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.37
    Path:     /Users/chriscardillo/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/chriscardillo/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/chriscardillo/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     /Users/chriscardillo/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/chriscardillo/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     /Users/chriscardillo/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/chriscardillo/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.15.1
    Path:     /Users/chriscardillo/.docker/cli-plugins/docker-scout

Server:
ERROR: Cannot connect to the Docker daemon at unix:///Users/chriscardillo/.docker/run/docker.sock. Is the docker daemon running?
errors pretty printing info

Diagnostics ID

2E63E3A6-3D8C-4351-872A-1C79C4A6B39B/20250129161513

Additional Info

No response

[ctalledo]

(CC @cdupuis).

@chriscardillo:

Sounds like you followed the steps in #7527 and ./check.sh /Applications/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd failed for you, so did a fresh install.

Question: before you did a fresh install, did you fully purge the prior Docker installation following the steps outlined in #7527?

#!/bin/bash

# Stop the docker services
echo "Stopping Docker..."
sudo pkill '[dD]ocker'

# Stop the vmnetd service
echo "Stopping com.docker.vmnetd service..."
sudo launchctl bootout system /Library/LaunchDaemons/com.docker.vmnetd.plist

# Stop the socket service
echo "Stopping com.docker.socket service..."
sudo launchctl bootout system /Library/LaunchDaemons/com.docker.socket.plist

# Remove vmnetd binary
echo "Removing com.docker.vmnetd binary..."
sudo rm -f /Library/PrivilegedHelperTools/com.docker.vmnetd

# Remove socket binary
echo "Removing com.docker.socket binary..."
sudo rm -f /Library/PrivilegedHelperTools/com.docker.socket

# Install new binaries
echo "Install new binaries..."
sudo cp /Applications/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd /Library/PrivilegedHelperTools/
sudo cp /Applications/Docker.app/Contents/MacOS/com.docker.socket /Library/PrivilegedHelperTools/

[RestlessWanderer]

I ran into this exact same issue on Sequoia 15.3 (Apple SI) starting yesterday, including the exact same check.sh output.

I was just able to get Docker Desktop re-installed after much messing around and combining multiple things. I'm not sure if everything I did contributed to it being re-installed successfully, but I'm not going to remove it and find out. Hopefully this works for you:

1. I ran the cli uninstall commands from here: https://docs.docker.com/desktop/uninstall/
   • When I did this, it sat at the terminal window for more than 15 minutes just showing "Uninstalling Docker Desktop...." and not doing anything else. I ended up breaking out (ctrl+c). It seemed to work though as when I tried to run the uninstall command again it failed with not finding the files to run.
   • I ran the two rm -rf commands.
   • Since the CLI uninstall didn't seem to go cleanly I still had the Docker icon in Applications, so I moved that to trash.
2. Rebooted my Mac.
3. I ran the commands from the Fix Startup Issue manual, Step 1 under Upgrade to Docker Desktop version 4.37.2 https://docs.docker.com/desktop/cert-revoke-solution/
   • Im not entirely sure it was necessary to do this, but it did confirm Docker was successfully removed before as the rm commands failed.
4. Downloaded the latest version of Docker Desktop and installed.
5. Launched Docker Desktop from Applications.
   • This time it actually launched the installation GUI to complete the installation.
6. After I ran through the prompts I was able to run docker info and docker version and get the proper output, without any of the Cannot connect to docker daemon errors.
7. Confirmed by launching vscode and my devcontainers built and loaded without issue.
   Hopefully this helps you. Good luck.