Docker Desktop not starting on macOS 12.3 on M1 #6568

MichaelVoelkel · 2022-11-10T18:50:39Z

I have tried with the latest version of Docker Desktop
I have tried disabling enabled experimental features
I have uploaded Diagnostics
Diagnostics ID:

Expected behavior

Docker desktop starts and diagnostic does not complain.

Actual behavior

Docker does nothing, in activity monitor I see it, but it does not respond after some time. App itself does not open and there is no icon.

Information

Not working works every time.

➜  ~ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check       
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?
[PASS] DD0001: is the application 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
[2022-11-10T18:46:45.409241000Z][com.docker.diagnose][I] ipc.NewClient: 397c3e4c-diagnose -> diagnosticd.sock diagnosticsd
[common/pkg/diagkit/gather/diagnose.glob..func12()
[	common/pkg/diagkit/gather/diagnose/linuxkit.go:18 +0x8c
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x104fd79a0)
[	common/pkg/diagkit/gather/diagnose/test.go:46 +0x40
[common/pkg/diagkit/gather/diagnose.Run.func1(0x104fd79a0)
[	common/pkg/diagkit/gather/diagnose/run.go:17 +0x40
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x4?, 0x104fd79a0)
[	common/pkg/diagkit/gather/diagnose/run.go:142 +0x80
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x104fd79a0, 0x140006a9718)
[	common/pkg/diagkit/gather/diagnose/run.go:151 +0x88
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x104fd7a20, 0x140006a9718)
[	common/pkg/diagkit/gather/diagnose/run.go:148 +0x50
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x104fd7b20, 0x140006a9718)
[	common/pkg/diagkit/gather/diagnose/run.go:148 +0x50
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x104fd7da0, 0x140006a9718)
[	common/pkg/diagkit/gather/diagnose/run.go:148 +0x50
[common/pkg/diagkit/gather/diagnose.walkOnce(0x104ab04a0?, 0x140003df890)
[	common/pkg/diagkit/gather/diagnose/run.go:137 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x104fd7da0, 0x140003f9300?, {0x140003dfb08, 0x1, 0x1})
[	common/pkg/diagkit/gather/diagnose/run.go:16 +0x160
[main.checkCmd({0x140001b2010?, 0x6?, 0x4?}, {0x0, 0x0})
[	common/cmd/com.docker.diagnose/main.go:133 +0xdc
[main.main()
[	common/cmd/com.docker.diagnose/main.go:99 +0x30c
[2022-11-10T18:46:45.409821000Z][com.docker.diagnose][I] (0ce37abc) 397c3e4c-diagnose C->S diagnosticsd GET /ping
[2022-11-10T18:46:45.411500000Z][com.docker.diagnose][W] (0ce37abc) 397c3e4c-diagnose C<-S NoResponse GET /ping (1.652875ms): 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
[2022-11-10T18:46:45.412108000Z][com.docker.diagnose][I] ipc.NewClient: 276ab14b-com.docker.diagnose -> lifecycle-server.sock VMDockerdAPI
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClientForPath(...)
[	linuxkit/pkg/desktop-host-tools/pkg/client/client.go:59
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClient({0x1048e5d09, 0x13})
[	linuxkit/pkg/desktop-host-tools/pkg/client/client.go:53 +0x90
[common/pkg/diagkit/gather/diagnose.isDockerEngineRunning()
[	common/pkg/diagkit/gather/diagnose/dockerd.go:21 +0x28
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x104fd7a20)
[	common/pkg/diagkit/gather/diagnose/test.go:46 +0x40
[common/pkg/diagkit/gather/diagnose.Run.func1(0x104fd7a20)
[	common/pkg/diagkit/gather/diagnose/run.go:17 +0x40
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x3?, 0x104fd7a20)
[	common/pkg/diagkit/gather/diagnose/run.go:142 +0x80
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x104fd7a20, 0x140006a9718)
[	common/pkg/diagkit/gather/diagnose/run.go:151 +0x88
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x104fd7b20, 0x140006a9718)
[	common/pkg/diagkit/gather/diagnose/run.go:148 +0x50
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x104fd7da0, 0x140006a9718)
[	common/pkg/diagkit/gather/diagnose/run.go:148 +0x50
[common/pkg/diagkit/gather/diagnose.walkOnce(0x104ab04a0?, 0x140003df890)
[	common/pkg/diagkit/gather/diagnose/run.go:137 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x104fd7da0, 0x140003f9300?, {0x140003dfb08, 0x1, 0x1})
[	common/pkg/diagkit/gather/diagnose/run.go:16 +0x160
[main.checkCmd({0x140001b2010?, 0x6?, 0x4?}, {0x0, 0x0})
[	common/cmd/com.docker.diagnose/main.go:133 +0xdc
[main.main()
[	common/cmd/com.docker.diagnose/main.go:99 +0x30c
[2022-11-10T18:46:45.412592000Z][com.docker.diagnose][I] (1f2c3ce3) 276ab14b-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2022-11-10T18:46:45.412815000Z][com.docker.diagnose][W] (1f2c3ce3) 276ab14b-com.docker.diagnose C<-S NoResponse GET /docker (222.209µs): Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-11-10T18:46:45.413000000Z][com.docker.diagnose][I] (1f2c3ce3-1) 276ab14b-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-11-10T18:46:45.413206000Z][com.docker.diagnose][W] (1f2c3ce3-1) 276ab14b-com.docker.diagnose C<-S NoResponse GET /ping (205.167µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-11-10T18:46:46.414576000Z][com.docker.diagnose][I] (1f2c3ce3-2) 276ab14b-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-11-10T18:46:46.416730000Z][com.docker.diagnose][W] (1f2c3ce3-2) 276ab14b-com.docker.diagnose C<-S NoResponse GET /ping (2.204667ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-11-10T18:46:47.417955000Z][com.docker.diagnose][I] (1f2c3ce3-3) 276ab14b-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-11-10T18:46:47.420188000Z][com.docker.diagnose][W] (1f2c3ce3-3) 276ab14b-com.docker.diagnose C<-S NoResponse GET /ping (2.233875ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-11-10T18:46:48.421277000Z][com.docker.diagnose][I] (1f2c3ce3-4) 276ab14b-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-11-10T18:46:48.423429000Z][com.docker.diagnose][W] (1f2c3ce3-4) 276ab14b-com.docker.diagnose C<-S NoResponse GET /ping (2.145625ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-11-10T18:46:49.424855000Z][com.docker.diagnose][I] (1f2c3ce3-5) 276ab14b-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-11-10T18:46:49.427147000Z][com.docker.diagnose][W] (1f2c3ce3-5) 276ab14b-com.docker.diagnose C<-S NoResponse GET /ping (2.282125ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-11-10T18:46:50.428549000Z][com.docker.diagnose][I] (1f2c3ce3-6) 276ab14b-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-11-10T18:46:50.430622000Z][com.docker.diagnose][W] (1f2c3ce3-6) 276ab14b-com.docker.diagnose C<-S NoResponse GET /ping (2.068167ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-11-10T18:46:51.433699000Z][com.docker.diagnose][I] (1f2c3ce3-7) 276ab14b-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-11-10T18:46:51.435836000Z][com.docker.diagnose][W] (1f2c3ce3-7) 276ab14b-com.docker.diagnose C<-S NoResponse GET /ping (2.166209ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-11-10T18:46:52.436847000Z][com.docker.diagnose][I] (1f2c3ce3-8) 276ab14b-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-11-10T18:46:52.439054000Z][com.docker.diagnose][W] (1f2c3ce3-8) 276ab14b-com.docker.diagnose C<-S NoResponse GET /ping (2.20375ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory

[FAIL] DD0015: are the binary symlinks installed? looking for /usr/local/bin/docker-index: lstat /usr/local/bin/docker-index: 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/michael/.docker/run/docker.sock. Is the docker daemon running?
[FAIL] DD0003: is the Docker CLI working? exit status 1
[FAIL] DD0014: are the backend processes running? 5 errors occurred:
	* vpnkit-bridge is not running
	* com.docker.vpnkit is not running
	* com.docker.driver.amd64-linux is not running
	* qemu-system-aarch64 is not running
	* 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: no such file or directory
[2022-11-10T18:46:53.639675000Z][com.docker.diagnose][I] ipc.NewClient: 74317d84-diagnose -> backend.sock BackendAPI
[common/pkg/backend.NewClientForPath({0x1048dd3f0?, 0x0?}, {0x140001a3040?, 0x1?})
[	common/pkg/backend/client.go:171 +0x3c
[common/pkg/backend.NewClient({0x1048dd3f0, 0x8})
[	common/pkg/backend/client.go:166 +0x54
[common/pkg/diagkit/gather/diagnose.glob..func8()
[	common/pkg/diagkit/gather/diagnose/ipc.go:25 +0x28
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x104fd7e20)
[	common/pkg/diagkit/gather/diagnose/test.go:46 +0x40
[common/pkg/diagkit/gather/diagnose.Run.func1(0x104fd7e20)
[	common/pkg/diagkit/gather/diagnose/run.go:17 +0x40
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x104fd7e20)
[	common/pkg/diagkit/gather/diagnose/run.go:142 +0x80
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x104fd7e20, 0x140006a9718)
[	common/pkg/diagkit/gather/diagnose/run.go:151 +0x88
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x104fd7da0, 0x140006a9718)
[	common/pkg/diagkit/gather/diagnose/run.go:148 +0x50
[common/pkg/diagkit/gather/diagnose.walkOnce(0x104ab04a0?, 0x140003df890)
[	common/pkg/diagkit/gather/diagnose/run.go:137 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x104fd7da0, 0x140003f9300?, {0x140003dfb08, 0x1, 0x1})
[	common/pkg/diagkit/gather/diagnose/run.go:16 +0x160
[main.checkCmd({0x140001b2010?, 0x6?, 0x4?}, {0x0, 0x0})
[	common/cmd/com.docker.diagnose/main.go:133 +0xdc
[main.main()
[	common/cmd/com.docker.diagnose/main.go:99 +0x30c

Here it hangs for a few minutes now.

The text was updated successfully, but these errors were encountered:

tholu · 2022-11-10T20:01:59Z

Same here after updating MacOS Ventura to 13.0.1 (22A400) on on M1 Mac Mini.

g1m0-enerbrain · 2022-11-11T09:35:34Z

After upgrading to Docker 4.14.0 issues about symlinks are found. It starts (I have MacOS 12.6.1 version on M1 chip).

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?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[FAIL] DD0015: are the binary symlinks installed? looking for /usr/local/bin/docker-index: lstat /usr/local/bin/docker-index: no such file or directory
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0012: is the VM networking working?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0019: is the com.docker.vmnetd process responding?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[WARN] DD0015: are the binary symlinks installed? looking for /usr/local/bin/docker-index: lstat /usr/local/bin/docker-index: no such file or directory
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?

Please note the following 1 warning:

1 : The check: are the binary symlinks installed?
Produced the following warning: looking for /usr/local/bin/docker-index: lstat /usr/local/bin/docker-index: no such file or directory

The symlinks to the docker CLI etc are needed for docker commands to work.

Please investigate the following 1 issue:

1 : The test: are the binary symlinks installed?
Failed with: looking for /usr/local/bin/docker-index: lstat /usr/local/bin/docker-index: no such file or directory

The symlinks to the docker CLI etc are needed for docker commands to work.

tholu · 2022-11-11T10:16:05Z

Manually updating to 4.14.0 (91374) solved it for me.

MichaelVoelkel · 2022-11-11T10:53:39Z

I just installed latest version from the website and removed the local one. So for me it's even for a new install...

DonRichards · 2022-11-11T21:34:32Z

Same. Fresh install today on a Mac Pro M1 Mac OS 12.6.1. Same error as posted for this ticket.

MichaelVoelkel · 2022-11-12T13:11:01Z

By the way, I would love to disable experimental features as a test, however: how? There are some CLI executables, so maybe one of them can be used?

DonRichards · 2022-11-14T15:24:40Z

~~Not sure if this helps but I ran the diagnostics command and this was the output.~~

In a nutshell it doesn't see /usr/local/bin/docker-index
Produced the following warning: looking for /usr/local/bin/docker-index: lstat /usr/local/bin/docker-index: no such file or directory
I was able to correct this error and it's not related. I still have the above error, this comment about docker-index missing was unrelated.

lucianthorr · 2022-12-02T15:06:19Z

@MichaelVoelkel If you're still stuck, I think you can edit the settings here to disable experimental features:
~/Library/Group\ Containers/group.com.docker/settings.json

Did you find any resolution? I may be in the same boat as you right now.

MichaelVoelkel · 2022-12-02T15:16:22Z

I followed some guide to remove docker entirely everywhere and reinstalled. This works!
However, why does Docker not come with a proper uninstaller itself? It sits down everywhere and that's hard to get rid off (sigh)
But, yeah solved by removing many, many files everywhere

geekzter · 2022-12-23T11:54:54Z

@MichaelVoelkel which guide did you follow?

MichaelVoelkel · 2022-12-23T12:12:33Z

I think this one: https://nektony.com/how-to/uninstall-docker-on-mac
at least it seems just as exhaustive as the one I used, probably it's exactly the same one. (WITHOUT using the tool mentioned somewhere at the bottom)

yaronuliel · 2023-01-24T11:47:42Z

@MichaelVoelkel Thanks! solved my issue too (I'm on Intel Chipset... BTW)

docker-robott · 2023-03-05T03:00:57Z

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

MichaelVoelkel closed this as completed Dec 2, 2022

docker locked and limited conversation to collaborators Mar 5, 2023

docker-robott added the lifecycle/locked label Mar 5, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Docker Desktop not starting on macOS 12.3 on M1 #6568

Docker Desktop not starting on macOS 12.3 on M1 #6568

MichaelVoelkel commented Nov 10, 2022

tholu commented Nov 10, 2022

g1m0-enerbrain commented Nov 11, 2022

tholu commented Nov 11, 2022

MichaelVoelkel commented Nov 11, 2022

DonRichards commented Nov 11, 2022 •

edited

Loading

MichaelVoelkel commented Nov 12, 2022

DonRichards commented Nov 14, 2022 •

edited

Loading

lucianthorr commented Dec 2, 2022

MichaelVoelkel commented Dec 2, 2022

geekzter commented Dec 23, 2022

MichaelVoelkel commented Dec 23, 2022 •

edited

Loading

yaronuliel commented Jan 24, 2023

docker-robott commented Mar 5, 2023

Docker Desktop not starting on macOS 12.3 on M1 #6568

Docker Desktop not starting on macOS 12.3 on M1 #6568

Comments

MichaelVoelkel commented Nov 10, 2022

Expected behavior

Actual behavior

Information

tholu commented Nov 10, 2022

g1m0-enerbrain commented Nov 11, 2022

tholu commented Nov 11, 2022

MichaelVoelkel commented Nov 11, 2022

DonRichards commented Nov 11, 2022 • edited Loading

MichaelVoelkel commented Nov 12, 2022

DonRichards commented Nov 14, 2022 • edited Loading

lucianthorr commented Dec 2, 2022

MichaelVoelkel commented Dec 2, 2022

geekzter commented Dec 23, 2022

MichaelVoelkel commented Dec 23, 2022 • edited Loading

yaronuliel commented Jan 24, 2023

docker-robott commented Mar 5, 2023

DonRichards commented Nov 11, 2022 •

edited

Loading

DonRichards commented Nov 14, 2022 •

edited

Loading

MichaelVoelkel commented Dec 23, 2022 •

edited

Loading