-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Desktop can't work on Macbook Pro 14 (M1 Pro) #6435
Comments
There seems to be a bug with the latest version of mac OS and docker desktop. See #6331. TLDR; the temporary workaround is to do a complete reinstall of docker. You can follow the cli steps here for the proper deletion, and reinstall docker either with Warning: all your existing containers, images and volumes will be deleted when you run the removal script. |
I've tried this way, but not work. |
It doesn't work for me either. |
I found the
|
And here is the
|
@chingxuds thanks for the stack trace (and sorry for the delay in replying). We recently merged a |
@djs55, I got similar problem, but exit code was 0. I'm on the Mac OS Ventura 13 beta 6. |
It works on version 4.11.1 now, thanks. |
The linked beta(?) build is not working for me. My diagnostic output looked a lot like the original poster, and the situation is been much the same however I'm on a 16inch MacBook Pro. 16inch MacBook Pro, Apple M1 Max, 64GB of RAM, macOS Monterey Version 12.6 (21G115) |
@techdragon the mentioned beta is already released. |
I have the same issue, random crashes of
|
Same here. Was crashing every couple of day, then everyday, and now multiple times a day |
Issue still reproducing with 4.14.1 (91661) Engine: 20.10.21 |
Similar to: #6530 VPNKit is looking at EXC_BAD_ACCESS (SIGSEGV) issue: moby/vpnkit#610 |
Thanks, issue seems to be fixed with Docker Engine 20.10.22. Update to Docker Desktop 4.16.0 or above. |
I updated to 4.16.0 (95345) and got the issue again. |
There hasn't been any activity on this issue for a long time. Prevent issues from auto-closing with a /lifecycle stale |
Expected behavior
Actual behavior
Information
Output of
/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?
[FAIL] DD0031: does the Docker API work? Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?
[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-07-31T13:52:37.197510000Z][com.docker.diagnose][I] ipc.NewClient: 90d452ca-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({0x1006bc6c8, 0x13})
[ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:53 +0x94
[common/pkg/diagkit/gather/diagnose.isDockerEngineRunning()
[ common/pkg/diagkit/gather/diagnose/dockerd.go:21 +0x2c
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x100da7740)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x100da7740)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x100da7840?, 0x100da7740)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x100da7740, 0x1400035f718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x100da7840?, 0x1400035f718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x20?, 0x1400035f718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkOnce(0x10087dee0?, 0x1400035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x100da7ac0, 0x14000313360?, {0x1400035fb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b4010?, 0x6?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0xe0
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x310
[2022-07-31T13:52:37.198364000Z][com.docker.diagnose][I] (f830335b) 90d452ca-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2022-07-31T13:52:37.198752000Z][com.docker.diagnose][W] (f830335b) 90d452ca-com.docker.diagnose C<-S NoResponse GET /docker (381.917µs): Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-07-31T13:52:37.199005000Z][com.docker.diagnose][I] (f830335b-1) 90d452ca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-07-31T13:52:37.199307000Z][com.docker.diagnose][W] (f830335b-1) 90d452ca-com.docker.diagnose C<-S NoResponse GET /ping (299.458µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-07-31T13:52:38.200441000Z][com.docker.diagnose][I] (f830335b-2) 90d452ca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-07-31T13:52:38.202325000Z][com.docker.diagnose][W] (f830335b-2) 90d452ca-com.docker.diagnose C<-S NoResponse GET /ping (1.894125ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-07-31T13:52:39.203184000Z][com.docker.diagnose][I] (f830335b-3) 90d452ca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-07-31T13:52:39.206934000Z][com.docker.diagnose][W] (f830335b-3) 90d452ca-com.docker.diagnose C<-S NoResponse GET /ping (3.741ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-07-31T13:52:40.209029000Z][com.docker.diagnose][I] (f830335b-4) 90d452ca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-07-31T13:52:40.210574000Z][com.docker.diagnose][W] (f830335b-4) 90d452ca-com.docker.diagnose C<-S NoResponse GET /ping (1.539792ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-07-31T13:52:41.211623000Z][com.docker.diagnose][I] (f830335b-5) 90d452ca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-07-31T13:52:41.213841000Z][com.docker.diagnose][W] (f830335b-5) 90d452ca-com.docker.diagnose C<-S NoResponse GET /ping (2.015708ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-07-31T13:52:42.215292000Z][com.docker.diagnose][I] (f830335b-6) 90d452ca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-07-31T13:52:42.216852000Z][com.docker.diagnose][W] (f830335b-6) 90d452ca-com.docker.diagnose C<-S NoResponse GET /ping (1.555458ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-07-31T13:52:43.217667000Z][com.docker.diagnose][I] (f830335b-7) 90d452ca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-07-31T13:52:43.218700000Z][com.docker.diagnose][W] (f830335b-7) 90d452ca-com.docker.diagnose C<-S NoResponse GET /ping (1.028541ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-07-31T13:52:44.219451000Z][com.docker.diagnose][I] (f830335b-8) 90d452ca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-07-31T13:52:44.220534000Z][com.docker.diagnose][W] (f830335b-8) 90d452ca-com.docker.diagnose C<-S NoResponse GET /ping (1.079ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: 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
[2022-07-31T13:52:44.224861000Z][com.docker.diagnose][I] ipc.NewClient: 2855b6d2-diagnose -> diagnosticd.sock diagnosticsd
[common/pkg/diagkit/gather/diagnose.glob..func12()
[ common/pkg/diagkit/gather/diagnose/linuxkit.go:18 +0x90
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x100da76c0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x100da76c0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x100da7740?, 0x100da76c0)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x100da76c0, 0x1400061f718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x100da7740?, 0x1400061f718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x100da7840?, 0x1400061f718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x20?, 0x1400061f718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkOnce(0x10087dee0?, 0x1400035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x100da7ac0, 0x14000313360?, {0x1400035fb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b4010?, 0x6?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0xe0
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x310
[2022-07-31T13:52:44.225716000Z][com.docker.diagnose][I] (50419df1) 2855b6d2-diagnose C->S diagnosticsd GET /ping
[2022-07-31T13:52:44.226035000Z][com.docker.diagnose][W] (50419df1) 2855b6d2-diagnose C<-S NoResponse GET /ping (315.917µs): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: 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
[PASS] DD0001: is the application running?
[PASS] DD0018: does the host support virtualization?
[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
[PASS] DD0015: are the binary symlinks installed?
^C[FAIL] DD0003: is the Docker CLI working? exit status 255
[2022-07-31T14:42:22.616854000Z][com.docker.diagnose][I] set ipc in shutting mode state
[PASS] DD0013: is the $PATH ok?
[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-07-31T14:42:22.625013000Z][com.docker.diagnose][I] ipc.NewClient: 045cf16b-diagnose -> backend.sock BackendAPI
[common/pkg/backend.NewClientForPath({0x1006b3e53?, 0x0?}, {0x140007985a0?, 0x1007b4638?})
[ common/pkg/backend/client.go:168 +0x40
[common/pkg/backend.NewClient({0x1006b3e53, 0x8})
[ common/pkg/backend/client.go:163 +0x58
[common/pkg/diagkit/gather/diagnose.glob..func8()
[ common/pkg/diagkit/gather/diagnose/ipc.go:25 +0x2c
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x100da7b40)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x100da7b40)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x100da7b40)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x100da7b40, 0x14000807718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x20?, 0x14000807718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkOnce(0x10087dee0?, 0x1400035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x100da7ac0, 0x14000313360?, {0x1400035fb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b4010?, 0x6?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0xe0
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x310
[FAIL] DD0014: are the backend processes running? 3 errors occurred:
* vpnkit-bridge is not running
* com.docker.vpnkit is not running
* com.docker.backend is not running
[FAIL] DD0008: is the native API responding? failed to ping tray application with error: Get "http://ipc/ping": dial unix backend.native.sock: connect: connection refused
[2022-07-31T14:42:24.213767000Z][com.docker.diagnose][I] ipc.NewClient: 73b3f15a-diagnose -> backend.native.sock SwiftAPI
[common/pkg/gui.NewClientForPath({0x1006b3e53?, 0x0?}, {0x140004943c0?, 0x1?})
[ common/pkg/gui/client.go:59 +0x40
[common/pkg/gui.NewClient({0x1006b3e53, 0x8})
[ common/pkg/gui/client.go:47 +0x58
[common/pkg/diagkit/gather/diagnose.glob..func9()
[ common/pkg/diagkit/gather/diagnose/ipc.go:40 +0x2c
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x100da7540)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x100da7540)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x100da7540)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x100da7540, 0x14000807718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x20?, 0x14000807718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkOnce(0x10087dee0?, 0x1400035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x100da7ac0, 0x14000313360?, {0x1400035fb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b4010?, 0x6?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0xe0
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x310
[2022-07-31T14:42:24.214716000Z][com.docker.diagnose][I] (0958abcb) 73b3f15a-diagnose C->S SwiftAPI GET /ping
[2022-07-31T14:42:24.215087000Z][com.docker.diagnose][W] (0958abcb) 73b3f15a-diagnose C<-S NoResponse GET /ping (366.75µs): Get "http://ipc/ping": dial unix backend.native.sock: connect: connection refused
[FAIL] DD0009: is the vpnkit API responding? dial unix vpnkit.diag.sock: connect: connection refused
[FAIL] DD0010: is the Docker API proxy responding? failed to ping Docker proxy API with error: Get "http://ipc/desktop-diagnostics/ping": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[2022-07-31T14:42:24.217141000Z][com.docker.diagnose][I] ipc.NewClient: 68632264-diagnose -> /.docker/run/docker.sock Proxy
[common/pkg/diagkit/gather/diagnose.glob..func11()
[ common/pkg/diagkit/gather/diagnose/ipc.go:91 +0x70
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x100da7c40)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x100da7c40)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x100da7c40)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x100da7c40, 0x14000807718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x20?, 0x14000807718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkOnce(0x10087dee0?, 0x1400035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x100da7ac0, 0x14000313360?, {0x1400035fb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b4010?, 0x6?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0xe0
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x310
[2022-07-31T14:42:24.217836000Z][com.docker.diagnose][I] (183c5df3) 68632264-diagnose C->S Proxy GET /desktop-diagnostics/ping
[2022-07-31T14:42:25.221121000Z][com.docker.diagnose][W] (183c5df3) 68632264-diagnose C<-S NoResponse GET /desktop-diagnostics/ping (1.003225708s): Get "http://ipc/desktop-diagnostics/ping": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[FAIL] DD0012: is the VM networking working? network checks failed: Post "http://ipc/check-network-connectivity": dial unix diagnosticd.sock: connect: no such file or directory
[2022-07-31T14:42:25.227291000Z][com.docker.diagnose][I] ipc.NewClient: 2da1c72b-diagnose-network -> diagnosticd.sock diagnosticsd
[common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK()
[ common/pkg/diagkit/gather/diagnose/network.go:34 +0xc8
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x100da7940)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x100da7940)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x100da7940)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x100da7940, 0x14000807718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x20?, 0x14000807718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkOnce(0x10087dee0?, 0x1400035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x100da7ac0, 0x14000313360?, {0x1400035fb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b4010?, 0x6?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0xe0
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x310
[2022-07-31T14:42:25.228383000Z][com.docker.diagnose][I] (f48f0241) 2da1c72b-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["10.10.10.109","10.211.55.2","10.37.129.2"]}
[2022-07-31T14:42:25.228969000Z][com.docker.diagnose][W] (f48f0241) 2da1c72b-diagnose-network C<-S NoResponse POST /check-network-connectivity (822µs): Post "http://ipc/check-network-connectivity": dial unix diagnosticd.sock: connect: no such file or directory
[FAIL] DD0032: do Docker networks overlap with host IPs? Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?
[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?
Please investigate the following 2 issues:
1 : The test: can a VM be started?
Failed with: vm has not started: failed to open kmsg.log: open log/vm/kmsg.log: no such file or directory
The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.
2 : The test: is the native API responding?
Failed with: failed to ping tray application with error: Get "http://ipc/ping": dial unix backend.native.sock: connect: connection refused
The native API server is needed to start Docker engine.
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: