Docker M1 suddenly freeze after startup, desktop app usable but not containers or CLI #6437
Comments
|
Noting that when i quit all Docker services from activity monitor and start it up again, the CPU usage kicks off and containers works for like 5 seconds (I can access them via localhost:xxxx), then it hangs. Nothing Accessible anymore. After Docker restarted, and containers are shown: after 5-10 seconds: |
|
I'm using version 4.8.1 of Docker for Mac, because it works. Currently, I'm afraid to update it because newer versions have bugs on Mac with M1 and nobody can confirm that they're resolved or not. :D |
|
@pwittchen Yeah, It seems that something specific happening in some of the containers causes whole docker-engine to freeze. Some containers causes this in 2 minutes and some in few hours. |
|
I have been experiencing the same thing with Apple M1 Pro : Monterey 12.5. I have tried all suggestions in #6435 and #6331 , including downgrading to 4.3.2 and 4.3. Nothing has worked for me, for all versions of docker-desktop it idles on startup. Remaining as "Docker is starting..." and even after a long period of time it does not resolve. I am open to suggestions on how to get a working version of docker, if not ill have to wait until they update it |
|
Apple M1 Pro : Monterey 12.5 |
|
Same issue. |
|
Me too. Happening when starting and/or restarting containers from vscode dev container plugin |
|
There hasn't been any activity on this issue for a long time. Prevent issues from auto-closing with a /lifecycle stale |
|
I'm on a Macbook M1 Max and am still experiencing this issue. |
|
Same issue here. I've had random hangs since version 4.13. Sometimes it ran for hours and in some phases it just started up and was broken within a couple of seconds. I've tried all combinations for filesystem, virtualization-framework, rosetta for emulation, but nothing helped. Best progress so far: 4.16.2 is telling "Docker Desktop stopping..." but will never finish. Will give 4.8.1 a try and see if I'm able to work again. |
|
Had the same situation (M1 Pro). With |
|
Ping @djs55 |
|
FYI: In my case Docker for Mac v4.17.0 works fine on Macbook Air with M1 and I cannot observe this bug anymore. |
|
Yes, 3 weeks and no issues. Seems to be resolved then for now. |
|
Same here, since 4.17.0 it's working! Thanks for you effort! |
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. /lifecycle locked |
Expected behavior
runs normally
Actual behavior
Docker desktop starts, auto start latest two containers I have (one used for portainer and the other my dev env)
Information
Output of
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check❯ /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? Get "http://docker.raw.sock/v1.24/containers/json?limit=0": context deadline exceeded
[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": read unix ->/Users/jihad/Library/Containers/com.docker.docker/Data/lifecycle-server.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:07:56.298908000Z][com.docker.diagnose][I] ipc.NewClient: 8b92e167-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({0x104b706c8, 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(0x10525b740)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x10525b740)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x10525b840?, 0x10525b740)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x10525b740, 0x140003df718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x10525b840?, 0x140003df718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x20?, 0x140003df718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkOnce(0x104d31ee0?, 0x140003df890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x10525bac0, 0x1400039b360?, {0x140003dfb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b6010?, 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-08-01T18:07:56.302358000Z][com.docker.diagnose][I] (d4010b91) 8b92e167-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2022-08-01T18:08:06.305082000Z][com.docker.diagnose][W] (d4010b91) 8b92e167-com.docker.diagnose C<-S NoResponse GET /docker (10.002469166s): Get "http://ipc/docker": read unix ->/Library/Containers/com.docker.docker/Data/lifecycle-server.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:08:06.323969000Z][com.docker.diagnose][I] (d4010b91-1) 8b92e167-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-08-01T18:08:07.327077000Z][com.docker.diagnose][W] (d4010b91-1) 8b92e167-com.docker.diagnose C<-S NoResponse GET /ping (1.003006334s): Get "http://ipc/ping": read unix ->/Library/Containers/com.docker.docker/Data/lifecycle-server.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:08:08.329711000Z][com.docker.diagnose][I] (d4010b91-2) 8b92e167-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-08-01T18:08:09.334151000Z][com.docker.diagnose][W] (d4010b91-2) 8b92e167-com.docker.diagnose C<-S NoResponse GET /ping (1.004371708s): Get "http://ipc/ping": read unix ->/Library/Containers/com.docker.docker/Data/lifecycle-server.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:08:10.336979000Z][com.docker.diagnose][I] (d4010b91-3) 8b92e167-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-08-01T18:08:11.342001000Z][com.docker.diagnose][W] (d4010b91-3) 8b92e167-com.docker.diagnose C<-S NoResponse GET /ping (1.004987833s): Get "http://ipc/ping": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:08:12.344205000Z][com.docker.diagnose][I] (d4010b91-4) 8b92e167-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-08-01T18:08:13.347955000Z][com.docker.diagnose][W] (d4010b91-4) 8b92e167-com.docker.diagnose C<-S NoResponse GET /ping (1.003711292s): Get "http://ipc/ping": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": read unix ->/Users/jihad/Library/Containers/com.docker.docker/Data/diagnosticd.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:08:13.355859000Z][com.docker.diagnose][I] ipc.NewClient: 2e1f7879-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(0x10525b6c0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x10525b6c0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x10525b740?, 0x10525b6c0)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x10525b6c0, 0x1400061f718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x10525b740?, 0x1400061f718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x10525b840?, 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(0x104d31ee0?, 0x140003df890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x10525bac0, 0x1400039b360?, {0x140003dfb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b6010?, 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-08-01T18:08:13.359632000Z][com.docker.diagnose][I] (0bd1d467) 2e1f7879-diagnose C->S diagnosticsd GET /ping
[2022-08-01T18:08:14.362374000Z][com.docker.diagnose][W] (0bd1d467) 2e1f7879-diagnose C<-S NoResponse GET /ping (1.00257375s): Get "http://ipc/ping": read unix ->/Library/Containers/com.docker.docker/Data/diagnosticd.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0017: can a VM be started?
[PASS] DD0015: are the binary symlinks installed?
^C[FAIL] DD0003: is the Docker CLI working? exit status 255
[2022-08-01T18:15:26.835732000Z][com.docker.diagnose][I] set ipc in shutting mode state
[PASS] DD0013: is the $PATH ok?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[FAIL] DD0012: is the VM networking working? network checks failed: Post "http://ipc/check-network-connectivity": read unix ->/Users/jihad/Library/Containers/com.docker.docker/Data/diagnosticd.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:15:28.093277000Z][com.docker.diagnose][I] ipc.NewClient: ba0e62f9-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(0x10525b940)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x10525b940)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x10525b940)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x10525b940, 0x140003c7718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x20?, 0x140003c7718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkOnce(0x104d31ee0?, 0x140003df890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x10525bac0, 0x1400039b360?, {0x140003dfb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b6010?, 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-08-01T18:15:28.094051000Z][com.docker.diagnose][I] (bd966eac) ba0e62f9-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["192.168.1.137","192.168.1.101"]}
[2022-08-01T18:15:33.095946000Z][com.docker.diagnose][W] (bd966eac) ba0e62f9-diagnose-network C<-S NoResponse POST /check-network-connectivity (5.001898042s): Post "http://ipc/check-network-connectivity": read unix ->/Library/Containers/com.docker.docker/Data/diagnosticd.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[FAIL] DD0032: do Docker networks overlap with host IPs? Get "http://docker.raw.sock/v1.24/networks": context deadline exceeded
[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: are the LinuxKit services running?
Failed with: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": read unix ->/Users/jihad/Library/Containers/com.docker.docker/Data/diagnosticd.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.
2 : The test: is the VM networking working?
Failed with: network checks failed: Post "http://ipc/check-network-connectivity": read unix ->/Users/jihad/Library/Containers/com.docker.docker/Data/diagnosticd.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
VM seems to have a network connectivity issue. Please check your host firewall and anti-virus settings in case they are blocking the VM.
❯ /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? Get "http://docker.raw.sock/v1.24/containers/json?limit=0": context deadline exceeded
[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:16:37.222924000Z][com.docker.diagnose][I] ipc.NewClient: 99cdb6f2-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({0x100c946c8, 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(0x10137f740)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x10137f740)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x10137f840?, 0x10137f740)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x10137f740, 0x1400035f718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x10137f840?, 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(0x100e55ee0?, 0x1400035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x10137fac0, 0x14000311360?, {0x1400035fb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b6010?, 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-08-01T18:16:37.225897000Z][com.docker.diagnose][I] (10d390a8) 99cdb6f2-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2022-08-01T18:16:47.229809000Z][com.docker.diagnose][W] (10d390a8) 99cdb6f2-com.docker.diagnose C<-S NoResponse GET /docker (10.0037265s): Get "http://ipc/docker": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:16:47.231392000Z][com.docker.diagnose][I] (10d390a8-1) 99cdb6f2-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-08-01T18:16:48.233812000Z][com.docker.diagnose][W] (10d390a8-1) 99cdb6f2-com.docker.diagnose C<-S NoResponse GET /ping (1.002311542s): Get "http://ipc/ping": read unix ->/Library/Containers/com.docker.docker/Data/lifecycle-server.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:16:49.235635000Z][com.docker.diagnose][I] (10d390a8-2) 99cdb6f2-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-08-01T18:16:50.237841000Z][com.docker.diagnose][W] (10d390a8-2) 99cdb6f2-com.docker.diagnose C<-S NoResponse GET /ping (1.002218917s): Get "http://ipc/ping": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:16:51.240178000Z][com.docker.diagnose][I] (10d390a8-3) 99cdb6f2-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-08-01T18:16:52.243281000Z][com.docker.diagnose][W] (10d390a8-3) 99cdb6f2-com.docker.diagnose C<-S NoResponse GET /ping (1.003098542s): Get "http://ipc/ping": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:16:53.248079000Z][com.docker.diagnose][I] (10d390a8-4) 99cdb6f2-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-08-01T18:16:54.251283000Z][com.docker.diagnose][W] (10d390a8-4) 99cdb6f2-com.docker.diagnose C<-S NoResponse GET /ping (1.003172166s): Get "http://ipc/ping": read unix ->/Library/Containers/com.docker.docker/Data/lifecycle-server.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": read unix ->/Users/jihad/Library/Containers/com.docker.docker/Data/diagnosticd.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[2022-08-01T18:16:54.255248000Z][com.docker.diagnose][I] ipc.NewClient: 7c8e3c55-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(0x10137f6c0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x10137f6c0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x10137f740?, 0x10137f6c0)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x10137f6c0, 0x1400061f718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x10137f740?, 0x1400061f718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x10137f840?, 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(0x100e55ee0?, 0x1400035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x10137fac0, 0x14000311360?, {0x1400035fb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b6010?, 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-08-01T18:16:54.257815000Z][com.docker.diagnose][I] (2359e499) 7c8e3c55-diagnose C->S diagnosticsd GET /ping
[2022-08-01T18:16:55.259779000Z][com.docker.diagnose][W] (2359e499) 7c8e3c55-diagnose C<-S NoResponse GET /ping (1.001930291s): Get "http://ipc/ping": read unix ->/Library/Containers/com.docker.docker/Data/diagnosticd.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0017: can a VM be started?
[PASS] DD0015: are the binary symlinks installed?
Error response from daemon: dial unix docker.raw.sock: connect: no such file or directory
[FAIL] DD0003: is the Docker CLI working? exit status 1
[PASS] DD0013: is the $PATH ok?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[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-08-01T18:20:10.948990000Z][com.docker.diagnose][I] ipc.NewClient: 7d2b497b-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(0x10137f940)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x44
[common/pkg/diagkit/gather/diagnose.Run.func1(0x10137f940)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x44
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x10137f940)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x84
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x10137f940, 0x1400059f718)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x3c
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x20?, 0x1400059f718)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x78
[common/pkg/diagkit/gather/diagnose.walkOnce(0x100e55ee0?, 0x1400035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x10137fac0, 0x14000311360?, {0x1400035fb08, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x164
[main.checkCmd({0x140001b6010?, 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-08-01T18:20:10.949832000Z][com.docker.diagnose][I] (7dcc78e1) 7d2b497b-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["192.168.1.137","192.168.1.101"]}
[2022-08-01T18:20:10.950189000Z][com.docker.diagnose][W] (7dcc78e1) 7d2b497b-diagnose-network C<-S NoResponse POST /check-network-connectivity (480µs): Post "http://ipc/check-network-connectivity": dial unix diagnosticd.sock: connect: no such file or directory
[2022-08-01T18:20:10.950456000Z][com.docker.diagnose][I] (7dcc78e1-1) 7d2b497b-diagnose-network C->S diagnosticsd GET /ping
[2022-08-01T18:20:10.950720000Z][com.docker.diagnose][W] (7dcc78e1-1) 7d2b497b-diagnose-network C<-S NoResponse GET /ping (262.208µs): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-08-01T18:20:11.956297000Z][com.docker.diagnose][I] (7dcc78e1-2) 7d2b497b-diagnose-network C->S diagnosticsd GET /ping
[2022-08-01T18:20:11.958410000Z][com.docker.diagnose][W] (7dcc78e1-2) 7d2b497b-diagnose-network C<-S NoResponse GET /ping (5.89475ms): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-08-01T18:20:12.964731000Z][com.docker.diagnose][I] (7dcc78e1-3) 7d2b497b-diagnose-network C->S diagnosticsd GET /ping
[2022-08-01T18:20:12.967535000Z][com.docker.diagnose][W] (7dcc78e1-3) 7d2b497b-diagnose-network C<-S NoResponse GET /ping (2.816375ms): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-08-01T18:20:13.969161000Z][com.docker.diagnose][I] (7dcc78e1-4) 7d2b497b-diagnose-network C->S diagnosticsd GET /ping
[2022-08-01T18:20:15.970990000Z][com.docker.diagnose][W] (7dcc78e1-4) 7d2b497b-diagnose-network C<-S NoResponse GET /ping (2.001784625s): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-08-01T18:20:16.972096000Z][com.docker.diagnose][I] (7dcc78e1-5) 7d2b497b-diagnose-network C->S diagnosticsd GET /ping
[2022-08-01T18:20:16.974376000Z][com.docker.diagnose][W] (7dcc78e1-5) 7d2b497b-diagnose-network C<-S NoResponse GET /ping (2.260292ms): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-08-01T18:20:17.975637000Z][com.docker.diagnose][I] (7dcc78e1-6) 7d2b497b-diagnose-network C->S diagnosticsd GET /ping
[2022-08-01T18:20:17.978347000Z][com.docker.diagnose][W] (7dcc78e1-6) 7d2b497b-diagnose-network C<-S NoResponse GET /ping (2.696333ms): Get "http://ipc/ping": 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: are the LinuxKit services running?
Failed with: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": read unix ->/Containers/com.docker.docker/Data/diagnosticd.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)
The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.
2 : The test: is the VM networking working?
Failed with: network checks failed: Post "http://ipc/check-network-connectivity": dial unix diagnosticd.sock: connect: no such file or directory
VM seems to have a network connectivity issue. Please check your host firewall and anti-virus settings in case they are blocking the VM.
Steps to reproduce the behavior
Currently, every time I force quit and run it again.
The text was updated successfully, but these errors were encountered: