Unable to start docker desktop on a M1 Mac

ferozed commented 1 year ago

Description

I am unable to start docker desktop on an M1 mac.

I have tried the following:

cleared all files that docker uses.
tried latest version
tried 4.19.0
tried 4.18.0

Reproduce

Download docker from https://docs.docker.com/desktop/release-notes/4.19
Run Docker... It just hangs.

Expected behavior

Docker desktop should start up.

LOGS com.docker.backend.log Docker.log

docker version

$ docker version
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Client:
 Cloud integration: v1.0.31
 Version:           20.10.24
 API version:       1.41
 Go version:        go1.19.7
 Git commit:        297e128
 Built:             Tue Apr  4 18:21:21 2023
 OS/Arch:           darwin/arm64
 Context:           default
 Experimental:      true

docker info

$ docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.10.4)
  compose: Docker Compose (Docker Inc., v2.17.2)
  dev: Docker Dev Environments (Docker Inc., v0.1.0)
  extension: Manages Docker extensions (Docker Inc., v0.2.19)
  init: Creates Docker-related starter files for your project (Docker Inc., v0.1.0-beta.2)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.25.0)
  scout: Command line tool for Docker Scout (Docker Inc., v0.9.0)

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

Diagnostics ID

CANT GET IT SINCE DOCKER DESKTOP DOESNT RUN

Additional Info

No response

bsousaa commented 1 year ago

Can you run the self-diagnose tool from the terminal /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check? What's the output?

Also suggest try the latest version of Docker Desktop: https://docs.docker.com/desktop/release-notes/

ChristianPavilonis commented 1 year ago

I've been having the same issue, I've uninstalled and reinstalled the latest. I'm not sure if the diagnostics are helpful because nothing is running, but here they are below:

[2023-07-05T02:08:09.562153000Z][com.docker.diagnose.paths][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0018: does the host support virtualization?
[FAIL] DD0001: is the application running? Docker is not running
[2023-07-05T02:08:09.562688000Z][com.docker.diagnose.ipc][I] ipc.NewClient: 16dbf10b-diagnose -> backend.sock BackendAPI
[2023-07-05T02:08:09.562751000Z][com.docker.diagnose.ipc][I] (02b9f7f4) 16dbf10b-diagnose C->S BackendAPI POST /idle/make-busy
[2023-07-05T02:08:09.563286000Z][com.docker.diagnose.ipc][W] (02b9f7f4) 16dbf10b-diagnose C<-S NoResponse POST /idle/make-busy (527.375µs): Post "http://ipc/idle/make-busy": dial unix backend.sock: connect: connection refused

[FAIL] DD0017: can a VM be started? vm has not started: failed to open kmsg.log: open log/vm/kmsg.log: no such file or directory
[FAIL] DD0016: is the LinuxKit VM running? vm is not running: failed to open kmsg.log: open log/vm/kmsg.log: no such file or directory
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2023-07-05T02:08:09.573691000Z][com.docker.diagnose.ipc][I] ipc.NewClient: a78e43a8-diagnose -> diagnosticd.sock diagnosticsd
[2023-07-05T02:08:09.573761000Z][com.docker.diagnose.ipc][I] (8c813441) a78e43a8-diagnose C->S diagnosticsd GET /ping
[2023-07-05T02:08:09.573952000Z][com.docker.diagnose.ipc][W] (8c813441) a78e43a8-diagnose C<-S NoResponse GET /ping (187.625µs): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory

[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T02:08:09.574060000Z][com.docker.diagnose.ipc][I] ipc.NewClient: 2cb5d50c-com.docker.diagnose -> lifecycle-server.sock VMDockerdAPI
[2023-07-05T02:08:09.574080000Z][com.docker.diagnose.ipc][I] (23a88b42) 2cb5d50c-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-07-05T02:08:09.574208000Z][com.docker.diagnose.ipc][W] (23a88b42) 2cb5d50c-com.docker.diagnose C<-S NoResponse GET /docker (126.416µs): Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T02:08:09.574224000Z][com.docker.diagnose.ipc][I] (23a88b42-1) 2cb5d50c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T02:08:09.574333000Z][com.docker.diagnose.ipc][W] (23a88b42-1) 2cb5d50c-com.docker.diagnose C<-S NoResponse GET /ping (107.542µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T02:08:10.575471000Z][com.docker.diagnose.ipc][I] (23a88b42-2) 2cb5d50c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T02:08:10.576617000Z][com.docker.diagnose.ipc][W] (23a88b42-2) 2cb5d50c-com.docker.diagnose C<-S NoResponse GET /ping (1.13225ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T02:08:11.577804000Z][com.docker.diagnose.ipc][I] (23a88b42-3) 2cb5d50c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T02:08:11.578912000Z][com.docker.diagnose.ipc][W] (23a88b42-3) 2cb5d50c-com.docker.diagnose C<-S NoResponse GET /ping (1.086166ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T02:08:12.580079000Z][com.docker.diagnose.ipc][I] (23a88b42-4) 2cb5d50c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T02:08:12.581066000Z][com.docker.diagnose.ipc][W] (23a88b42-4) 2cb5d50c-com.docker.diagnose C<-S NoResponse GET /ping (968.209µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T02:08:13.582258000Z][com.docker.diagnose.ipc][I] (23a88b42-5) 2cb5d50c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T02:08:13.583193000Z][com.docker.diagnose.ipc][W] (23a88b42-5) 2cb5d50c-com.docker.diagnose C<-S NoResponse GET /ping (917.958µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T02:08:14.584379000Z][com.docker.diagnose.ipc][I] (23a88b42-6) 2cb5d50c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T02:08:14.585347000Z][com.docker.diagnose.ipc][W] (23a88b42-6) 2cb5d50c-com.docker.diagnose C<-S NoResponse GET /ping (968.833µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T02:08:15.586420000Z][com.docker.diagnose.ipc][I] (23a88b42-7) 2cb5d50c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T02:08:15.587327000Z][com.docker.diagnose.ipc][W] (23a88b42-7) 2cb5d50c-com.docker.diagnose C<-S NoResponse GET /ping (892.541µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T02:08:16.588498000Z][com.docker.diagnose.ipc][I] (23a88b42-8) 2cb5d50c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T02:08:16.589599000Z][com.docker.diagnose.ipc][W] (23a88b42-8) 2cb5d50c-com.docker.diagnose C<-S NoResponse GET /ping (1.086041ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory

[FAIL] DD0015: are the binary symlinks installed? 2 errors occurred:
    * checking binaries in /usr/local/bin: looking for /usr/local/bin/docker: lstat /usr/local/bin/docker: no such file or directory
    * checking binaries in $HOME/.docker/bin: unable to find /Users/christian/.docker/bin: stat /Users/christian/.docker/bin: no such file or directory

[FAIL] DD0031: does the Docker API work? Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?
[PASS] DD0013: is the $PATH ok?
Cannot connect to the Docker daemon at unix:///Users/christian/.docker/run/docker.sock. Is the docker daemon running?
[FAIL] DD0003: is the Docker CLI working? exit status 1
[FAIL] DD0038: is the connection to Docker working? HTTP GET https://login.docker.com: Get "https://login.docker.com": proxyconnect tcp: dial unix httpproxy.sock: connect: no such file or directory
[FAIL] DD0014: are the backend processes running? 1 error occurred:
    * com.docker.backend is not running

[FAIL] DD0007: is the backend responding? failed to ping com.docker.backend with error: Get "http://ipc/ping": dial unix backend.sock: connect: connection refused
[2023-07-05T02:08:16.631987000Z][com.docker.diagnose.ipc][I] ipc.NewClient: 055c2c33-diagnose -> backend.sock BackendAPI

mbresch-sf commented 1 year ago

I'm stuck on the same problem and have nearly the same diagnostic output like Christian have:

/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
[2023-07-05T09:23:14.972388000Z][com.docker.diagnose.paths][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0018: does the host support virtualization?
[FAIL] DD0001: is the application running? Docker is not running
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2023-07-05T09:23:14.999363000Z][com.docker.diagnose.ipc][I] ipc.NewClient: 1ea89d7f-diagnose -> diagnosticd.sock diagnosticsd
[2023-07-05T09:23:14.999406000Z][com.docker.diagnose.ipc][I] (365d764d) 1ea89d7f-diagnose C->S diagnosticsd GET /ping
[2023-07-05T09:23:14.999571000Z][com.docker.diagnose.ipc][W] (365d764d) 1ea89d7f-diagnose C<-S NoResponse GET /ping (160.125µs): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory

[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T09:23:14.999802000Z][com.docker.diagnose.ipc][I] ipc.NewClient: 7568dcf4-com.docker.diagnose -> lifecycle-server.sock VMDockerdAPI
[2023-07-05T09:23:14.999826000Z][com.docker.diagnose.ipc][I] (c72ed416) 7568dcf4-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-07-05T09:23:14.999953000Z][com.docker.diagnose.ipc][W] (c72ed416) 7568dcf4-com.docker.diagnose C<-S NoResponse GET /docker (128.041µs): Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T09:23:14.999967000Z][com.docker.diagnose.ipc][I] (c72ed416-1) 7568dcf4-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T09:23:15.000071000Z][com.docker.diagnose.ipc][W] (c72ed416-1) 7568dcf4-com.docker.diagnose C<-S NoResponse GET /ping (104.459µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T09:23:16.001240000Z][com.docker.diagnose.ipc][I] (c72ed416-2) 7568dcf4-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T09:23:16.002587000Z][com.docker.diagnose.ipc][W] (c72ed416-2) 7568dcf4-com.docker.diagnose C<-S NoResponse GET /ping (1.296416ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T09:23:17.003758000Z][com.docker.diagnose.ipc][I] (c72ed416-3) 7568dcf4-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T09:23:17.004482000Z][com.docker.diagnose.ipc][W] (c72ed416-3) 7568dcf4-com.docker.diagnose C<-S NoResponse GET /ping (711.667µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T09:23:18.005578000Z][com.docker.diagnose.ipc][I] (c72ed416-4) 7568dcf4-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T09:23:18.006475000Z][com.docker.diagnose.ipc][W] (c72ed416-4) 7568dcf4-com.docker.diagnose C<-S NoResponse GET /ping (870.209µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T09:23:19.007634000Z][com.docker.diagnose.ipc][I] (c72ed416-5) 7568dcf4-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T09:23:19.008876000Z][com.docker.diagnose.ipc][W] (c72ed416-5) 7568dcf4-com.docker.diagnose C<-S NoResponse GET /ping (1.211541ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T09:23:20.010045000Z][com.docker.diagnose.ipc][I] (c72ed416-6) 7568dcf4-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T09:23:20.011069000Z][com.docker.diagnose.ipc][W] (c72ed416-6) 7568dcf4-com.docker.diagnose C<-S NoResponse GET /ping (1.012416ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T09:23:21.012208000Z][com.docker.diagnose.ipc][I] (c72ed416-7) 7568dcf4-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T09:23:21.013223000Z][com.docker.diagnose.ipc][W] (c72ed416-7) 7568dcf4-com.docker.diagnose C<-S NoResponse GET /ping (997.083µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-07-05T09:23:22.013645000Z][com.docker.diagnose.ipc][I] (c72ed416-8) 7568dcf4-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-07-05T09:23:22.014856000Z][com.docker.diagnose.ipc][W] (c72ed416-8) 7568dcf4-com.docker.diagnose C<-S NoResponse GET /ping (1.242042ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory

[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?
[PASS] DD0013: is the $PATH ok?
Cannot connect to the Docker daemon at unix:///Users/mbr/.docker/run/docker.sock. Is the docker daemon running?
[FAIL] DD0003: is the Docker CLI working? exit status 1
[FAIL] DD0038: is the connection to Docker working? HTTP GET https://login.docker.com: Get "https://login.docker.com": proxyconnect tcp: dial unix httpproxy.sock: connect: no such file or directory
[FAIL] DD0014: are the backend processes running? 1 error occurred:
    * com.docker.backend is not running

[FAIL] DD0007: is the backend responding? failed to ping com.docker.backend with error: Get "http://ipc/ping": dial unix backend.sock: connect: connection refused
[2023-07-05T09:23:22.130115000Z][com.docker.diagnose.ipc][I] ipc.NewClient: c0d2ad07-diagnose -> backend.sock BackendAPI

bsousaa commented 1 year ago

Can you try a Factory Reset under the Troubleshoot menu? https://docs.docker.com/desktop/troubleshoot/overview/

ChristianPavilonis commented 1 year ago

@bsousaa I can't because I can't launch at all. I've deleted as many things to do with docker as possible.

rm -rf ~/Library/Containers/com.docker.docker
rm -rf ~/.docker
rm -rf /usr/local/bin/docker
rm -rf /Library/PrivilegedHelperTools/com.docker.vmnetd
sudo rm -rf /Library/Application\ Support/Docker

rm -rf ~/Library/Group\ Containers/group.com.docker
sudo rm /Library/LaunchDaemons/com.docker.vmnetd.plist

mbresch-sf commented 1 year ago

My Docker Desktop is not starting. I can't reach the Troubleshoot menu. :-(

ChristianPavilonis commented 1 year ago

🤔 I uninstalled via command line and reinstalled and now it's working.

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

ferozed commented 1 year ago

After a couple of uninstalls/reinstalls, I rebooted the machine. Then it started working.

Ye old three finger salute.

paulosandinof commented 1 year ago

I'm having the same issue. Docker doesn't start at all. Reinstalled dozen of times and nothing works.

bsousaa commented 1 year ago

@paulosandinof can you share more context about the failure? Is this happening after an update? Please submit a diagnostics by running in the terminal /Applications/Docker.app/Contents/MacOS/com.docker.diagnose gather -upload.

paulosandinof commented 1 year ago

Ok, this started happening after an MacOS update (at least I noticed after this). I cannot open Docker from the icon on the menu. At version 4.20 it threw an error saying "Docker backend cannot start; Exit code 1". After I updated today to 4.21, the application just hangs and doesn't open. The strange thing is, when I explore the contents of the Docker package, and click on the icon, the application loads.

I run the diagnostics, it uploaded on this link: https://docker-pinata-support.s3.amazonaws.com/incoming/3/FEF9831D-E114-48E1-9393-06751B1BAC9F/20230706133130.zip

ChristianPavilonis commented 1 year ago

Update: docker desktop stopped working, again wouldn't launch, uninstalled & reinstalled the same way I did earlier, and seems to be working again 😩

bsousaa commented 1 year ago

Few things. Can you please give the output of the following commands:

osascript -e 'user locale of (get system info)'
echo $PATH; which sw_vers; sw_vers
docker ps

leonboot commented 1 year ago

Having the exact same issue, since running Docker Desktop on my new Apple Silicon Mac. I'll share the output of the above commands: nl_NL (changing the OS country/region to en_US made no difference)

/usr/local/opt/mysql-client/bin:/Users/[redacted]/google-cloud-sdk/bin:/Users/[redacted]/.gem/ruby/2.6.0/bin:/Users/[redacted]/bin:/Users/[redacted]/.symfony/bin:/Users/[redacted]/.composer/vendor/bin:/usr/local/sbin:/Users/[redacted]/.nvm/versions/node/v18.17.0/bin:/Users/[redacted]/google-cloud-sdk/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin:/Library/Apple/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/[redacted]/go/bin:/Users/[redacted]/Library/Android/sdk/platform-tools
/usr/bin/sw_vers
ProductName:        macOS
ProductVersion:     13.4.1
ProductVersionExtra:    (c)
BuildVersion:       22F770820d

And the final command, as expected:

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

I also tried starting the Docker Desktop app from the command line. It quit straight away, showing one message on the console:

➜  ~ /Applications/Docker.app/Contents/MacOS/Docker\ Desktop.app/Contents/MacOS/Docker\ Desktop 
[bugsnag] Loaded!

Hope this helps. I'm very dependent on Docker for my daily routine, so until this is fixed I'll have to keep the new Apple Silicon MacBook on the shelf.

mbresch-sf commented 1 year ago

When docker desktop does not start my workaround for now is to open the Activity Monitor, search for docker an kill the process immediately. Open docker again.

xgt001 commented 1 year ago

Thanks @mbresch-sf for this workaround, its a bit sad about having to resort to this esoteric way of addressing the issue, which has been open for about 3 weeks now :(

Addition: After removing and reinstalling Docker for mac, I had to kill Docker and com.docker.backend from activity monitor as well a bunch of times. Now it works. I will upload diagnostic when I get a chance

nathancarter commented 11 months ago

I have this same problem, which also shows up in #6822 and #6142 in various flavors. Specifically, without any major changes that I know of to Docker or my OS, Docker started hanging upon launch, requiring Activity Monitor to close it. I've tried:

Killing everything with Activity Monitor and restarting Docker.
Rebooting the machine.
Reinstalling Docker with the latest build from the website.
Reinstalling Docker using a homebrew cask.
Deleting all Docker configuration files, images, settings, and symbolic links using a script posted in another GitHub issue.
Many combinations of the above in various sequences.

There are many errors when I run various types of configuration checks. See the uploaded diagnostics here: 31FF3A23-BBD2-459C-902B-B961E8C8B5C7/20231006180935

docker / for-mac