Docker Desktop says "Fatal Error: exit status 1" and refuses to start

[timmattison]

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

I can't upload diagnostics because it just hangs where it says "Diagnosing..."

Expected behavior

I should start Docker Desktop and it should let me use Docker

Actual behavior

Docker Desktop says "Fatal Error: exit status 1". It gives me the option to reset to factory defaults, diagnose, or exit. I've reset to factory defaults, uninstalled, reinstalled an older version (4.12), rebooted, and it always says the same thing.

Information

This happened when Docker ran out of space on my system. I tried to move the data directory to another drive, that hung and I had to kill Docker, now nothing works.

• macOS Version: 12.6
• Intel chip or Apple chip: Apple M1 chip
• Docker Desktop Version: 4.12 and 4.13

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?
[SKIP] 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-10-20T22:29:58.024936000Z][com.docker.diagnose][I] ipc.NewClient: 344e44d6-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({0x104dade20, 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(0x1054bb940)
[	common/pkg/diagkit/gather/diagnose/test.go:46 +0x40
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1054bb940)
[	common/pkg/diagkit/gather/diagnose/run.go:17 +0x40
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x1054bba40?, 0x1054bb940)
[	common/pkg/diagkit/gather/diagnose/run.go:140 +0x80
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1054bb940, 0x1400061f718)
[	common/pkg/diagkit/gather/diagnose/run.go:146 +0x38
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1054bba40?, 0x1400061f718)
[	common/pkg/diagkit/gather/diagnose/run.go:149 +0x74
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1047f152c?, 0x1400061f718)
[	common/pkg/diagkit/gather/diagnose/run.go:149 +0x74
[common/pkg/diagkit/gather/diagnose.walkOnce(0x104f79660?, 0x1400061f890)
[	common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x1054bbcc0, 0x12cc0ffff?, {0x1400061fb08, 0x1, 0x1})
[	common/pkg/diagkit/gather/diagnose/run.go:16 +0x160
[main.checkCmd({0x140001b4010?, 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-10-20T22:29:58.025963000Z][com.docker.diagnose][I] (8d4b7fdd) 344e44d6-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2022-10-20T22:29:58.026401000Z][com.docker.diagnose][W] (8d4b7fdd) 344e44d6-com.docker.diagnose C<-S NoResponse GET /docker (434.125µs): Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-10-20T22:29:58.026622000Z][com.docker.diagnose][I] (8d4b7fdd-1) 344e44d6-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-20T22:29:58.026892000Z][com.docker.diagnose][W] (8d4b7fdd-1) 344e44d6-com.docker.diagnose C<-S NoResponse GET /ping (268.417µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-10-20T22:29:59.028061000Z][com.docker.diagnose][I] (8d4b7fdd-2) 344e44d6-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-20T22:29:59.029980000Z][com.docker.diagnose][W] (8d4b7fdd-2) 344e44d6-com.docker.diagnose C<-S NoResponse GET /ping (1.940875ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-10-20T22:30:00.031237000Z][com.docker.diagnose][I] (8d4b7fdd-3) 344e44d6-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-20T22:30:00.033105000Z][com.docker.diagnose][W] (8d4b7fdd-3) 344e44d6-com.docker.diagnose C<-S NoResponse GET /ping (1.861292ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-10-20T22:30:01.034461000Z][com.docker.diagnose][I] (8d4b7fdd-4) 344e44d6-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-20T22:30:01.036154000Z][com.docker.diagnose][W] (8d4b7fdd-4) 344e44d6-com.docker.diagnose C<-S NoResponse GET /ping (1.675416ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-10-20T22:30:02.037039000Z][com.docker.diagnose][I] (8d4b7fdd-5) 344e44d6-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-20T22:30:02.039391000Z][com.docker.diagnose][W] (8d4b7fdd-5) 344e44d6-com.docker.diagnose C<-S NoResponse GET /ping (2.346375ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-10-20T22:30:03.040389000Z][com.docker.diagnose][I] (8d4b7fdd-6) 344e44d6-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-20T22:30:03.042307000Z][com.docker.diagnose][W] (8d4b7fdd-6) 344e44d6-com.docker.diagnose C<-S NoResponse GET /ping (1.882917ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-10-20T22:30:04.043223000Z][com.docker.diagnose][I] (8d4b7fdd-7) 344e44d6-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-20T22:30:04.045691000Z][com.docker.diagnose][W] (8d4b7fdd-7) 344e44d6-com.docker.diagnose C<-S NoResponse GET /ping (2.459041ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2022-10-20T22:30:05.049874000Z][com.docker.diagnose][I] (8d4b7fdd-8) 344e44d6-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-20T22:30:05.051645000Z][com.docker.diagnose][W] (8d4b7fdd-8) 344e44d6-com.docker.diagnose C<-S NoResponse GET /ping (1.7645ms): 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-10-20T22:30:05.055327000Z][com.docker.diagnose][I] ipc.NewClient: 70234c02-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(0x1054bb8c0)
[	common/pkg/diagkit/gather/diagnose/test.go:46 +0x40
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1054bb8c0)
[	common/pkg/diagkit/gather/diagnose/run.go:17 +0x40
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x1054bb940?, 0x1054bb8c0)
[	common/pkg/diagkit/gather/diagnose/run.go:140 +0x80
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x1054bb8c0, 0x14000251718)
[	common/pkg/diagkit/gather/diagnose/run.go:146 +0x38
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1054bb940?, 0x14000251718)
[	common/pkg/diagkit/gather/diagnose/run.go:149 +0x74
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1054bba40?, 0x14000251718)
[	common/pkg/diagkit/gather/diagnose/run.go:149 +0x74
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1047f152c?, 0x14000251718)
[	common/pkg/diagkit/gather/diagnose/run.go:149 +0x74
[common/pkg/diagkit/gather/diagnose.walkOnce(0x104f79660?, 0x1400061f890)
[	common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x1054bbcc0, 0x12cc0ffff?, {0x1400061fb08, 0x1, 0x1})
[	common/pkg/diagkit/gather/diagnose/run.go:16 +0x160
[main.checkCmd({0x140001b4010?, 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-10-20T22:30:05.057406000Z][com.docker.diagnose][I] (4ca943df) 70234c02-diagnose C->S diagnosticsd GET /ping
[2022-10-20T22:30:05.058303000Z][com.docker.diagnose][W] (4ca943df) 70234c02-diagnose C<-S NoResponse GET /ping (890.333µ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?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
[FAIL] DD0003: is the Docker CLI working? exit status 1
[PASS] DD0013: is the $PATH ok?
[PASS] DD0007: is the backend responding?
[FAIL] DD0014: are the backend processes running? 4 errors occurred:
	* com.docker.vpnkit is not running
	* com.docker.driver.amd64-linux is not running
	* qemu-system-aarch64 is not running
	* vpnkit-bridge is not running


[PASS] DD0008: is the native API responding?
[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": dial unix /Users/timmattison/.docker/run/docker.sock: connect: connection refused
[2022-10-20T22:30:14.085856000Z][com.docker.diagnose][I] ipc.NewClient: 88bc6916-diagnose -> <HOME>/.docker/run/docker.sock Proxy
[common/pkg/diagkit/gather/diagnose.glob..func11()
[	common/pkg/diagkit/gather/diagnose/ipc.go:91 +0x6c
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x1054bbe40)
[	common/pkg/diagkit/gather/diagnose/test.go:46 +0x40
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1054bbe40)
[	common/pkg/diagkit/gather/diagnose/run.go:17 +0x40
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x1054bbe40)
[	common/pkg/diagkit/gather/diagnose/run.go:140 +0x80
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1054bbe40, 0x14000431718)
[	common/pkg/diagkit/gather/diagnose/run.go:146 +0x38
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1047f152c?, 0x14000431718)
[	common/pkg/diagkit/gather/diagnose/run.go:149 +0x74
[common/pkg/diagkit/gather/diagnose.walkOnce(0x104f79660?, 0x1400061f890)
[	common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x1054bbcc0, 0x12cc0ffff?, {0x1400061fb08, 0x1, 0x1})
[	common/pkg/diagkit/gather/diagnose/run.go:16 +0x160
[main.checkCmd({0x140001b4010?, 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-10-20T22:30:14.086453000Z][com.docker.diagnose][I] (f94c4c87) 88bc6916-diagnose C->S Proxy GET /desktop-diagnostics/ping
[2022-10-20T22:30:14.086740000Z][com.docker.diagnose][W] (f94c4c87) 88bc6916-diagnose C<-S NoResponse GET /desktop-diagnostics/ping (284.167µs): Get "http://ipc/desktop-diagnostics/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2022-10-20T22:30:14.086960000Z][com.docker.diagnose][I] (f94c4c87-1) 88bc6916-diagnose C->S Proxy GET /ping
[2022-10-20T22:30:14.087193000Z][com.docker.diagnose][W] (f94c4c87-1) 88bc6916-diagnose C<-S NoResponse GET /ping (231.667µs): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2022-10-20T22:30:15.087756000Z][com.docker.diagnose][I] (f94c4c87-2) 88bc6916-diagnose C->S Proxy GET /ping
[2022-10-20T22:30:15.089946000Z][com.docker.diagnose][W] (f94c4c87-2) 88bc6916-diagnose C<-S NoResponse GET /ping (2.182625ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2022-10-20T22:30:16.091883000Z][com.docker.diagnose][I] (f94c4c87-3) 88bc6916-diagnose C->S Proxy GET /ping
[2022-10-20T22:30:16.093615000Z][com.docker.diagnose][W] (f94c4c87-3) 88bc6916-diagnose C<-S NoResponse GET /ping (1.721875ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2022-10-20T22:30:17.094953000Z][com.docker.diagnose][I] (f94c4c87-4) 88bc6916-diagnose C->S Proxy GET /ping
[2022-10-20T22:30:17.097437000Z][com.docker.diagnose][W] (f94c4c87-4) 88bc6916-diagnose C<-S NoResponse GET /ping (2.476292ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2022-10-20T22:30:18.098343000Z][com.docker.diagnose][I] (f94c4c87-5) 88bc6916-diagnose C->S Proxy GET /ping
[2022-10-20T22:30:18.099593000Z][com.docker.diagnose][W] (f94c4c87-5) 88bc6916-diagnose C<-S NoResponse GET /ping (1.243291ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2022-10-20T22:30:19.100550000Z][com.docker.diagnose][I] (f94c4c87-6) 88bc6916-diagnose C->S Proxy GET /ping
[2022-10-20T22:30:19.102213000Z][com.docker.diagnose][W] (f94c4c87-6) 88bc6916-diagnose C<-S NoResponse GET /ping (1.657167ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2022-10-20T22:30:20.103071000Z][com.docker.diagnose][I] (f94c4c87-7) 88bc6916-diagnose C->S Proxy GET /ping
[2022-10-20T22:30:20.104874000Z][com.docker.diagnose][W] (f94c4c87-7) 88bc6916-diagnose C<-S NoResponse GET /ping (1.794ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2022-10-20T22:30:21.105887000Z][com.docker.diagnose][I] (f94c4c87-8) 88bc6916-diagnose C->S Proxy GET /ping
[2022-10-20T22:30:21.107562000Z][com.docker.diagnose][W] (f94c4c87-8) 88bc6916-diagnose C<-S NoResponse GET /ping (1.671041ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused

[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-10-20T22:30:21.111692000Z][com.docker.diagnose][I] ipc.NewClient: cc0da2a6-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(0x1054bbb40)
[	common/pkg/diagkit/gather/diagnose/test.go:46 +0x40
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1054bbb40)
[	common/pkg/diagkit/gather/diagnose/run.go:17 +0x40
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x1054bbb40)
[	common/pkg/diagkit/gather/diagnose/run.go:140 +0x80
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1054bbb40, 0x14000431718)
[	common/pkg/diagkit/gather/diagnose/run.go:146 +0x38
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1047f152c?, 0x14000431718)
[	common/pkg/diagkit/gather/diagnose/run.go:149 +0x74
[common/pkg/diagkit/gather/diagnose.walkOnce(0x104f79660?, 0x1400061f890)
[	common/pkg/diagkit/gather/diagnose/run.go:135 +0x8c
[common/pkg/diagkit/gather/diagnose.Run(0x1054bbcc0, 0x12cc0ffff?, {0x1400061fb08, 0x1, 0x1})
[	common/pkg/diagkit/gather/diagnose/run.go:16 +0x160
[main.checkCmd({0x140001b4010?, 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-10-20T22:30:21.114323000Z][com.docker.diagnose][I] (13c815ca) cc0da2a6-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["192.168.0.173","100.94.15.123"]}
[2022-10-20T22:30:21.115247000Z][com.docker.diagnose][W] (13c815ca) cc0da2a6-diagnose-network C<-S NoResponse POST /check-network-connectivity (1.490917ms): Post "http://ipc/check-network-connectivity": dial unix diagnosticd.sock: connect: no such file or directory
[2022-10-20T22:30:21.115515000Z][com.docker.diagnose][I] (13c815ca-1) cc0da2a6-diagnose-network C->S diagnosticsd GET /ping
[2022-10-20T22:30:21.115787000Z][com.docker.diagnose][W] (13c815ca-1) cc0da2a6-diagnose-network C<-S NoResponse GET /ping (270.292µs): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-10-20T22:30:22.117107000Z][com.docker.diagnose][I] (13c815ca-2) cc0da2a6-diagnose-network C->S diagnosticsd GET /ping
[2022-10-20T22:30:22.118853000Z][com.docker.diagnose][W] (13c815ca-2) cc0da2a6-diagnose-network C<-S NoResponse GET /ping (1.743542ms): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-10-20T22:30:23.119897000Z][com.docker.diagnose][I] (13c815ca-3) cc0da2a6-diagnose-network C->S diagnosticsd GET /ping
[2022-10-20T22:30:23.120763000Z][com.docker.diagnose][W] (13c815ca-3) cc0da2a6-diagnose-network C<-S NoResponse GET /ping (862.583µs): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-10-20T22:30:24.121349000Z][com.docker.diagnose][I] (13c815ca-4) cc0da2a6-diagnose-network C->S diagnosticsd GET /ping
[2022-10-20T22:30:24.122683000Z][com.docker.diagnose][W] (13c815ca-4) cc0da2a6-diagnose-network C<-S NoResponse GET /ping (1.326916ms): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-10-20T22:30:25.123585000Z][com.docker.diagnose][I] (13c815ca-5) cc0da2a6-diagnose-network C->S diagnosticsd GET /ping
[2022-10-20T22:30:25.124975000Z][com.docker.diagnose][W] (13c815ca-5) cc0da2a6-diagnose-network C<-S NoResponse GET /ping (1.382917ms): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-10-20T22:30:26.125948000Z][com.docker.diagnose][I] (13c815ca-6) cc0da2a6-diagnose-network C->S diagnosticsd GET /ping
[2022-10-20T22:30:26.127288000Z][com.docker.diagnose][W] (13c815ca-6) cc0da2a6-diagnose-network C<-S NoResponse GET /ping (1.333792ms): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-10-20T22:30:27.128157000Z][com.docker.diagnose][I] (13c815ca-7) cc0da2a6-diagnose-network C->S diagnosticsd GET /ping
[2022-10-20T22:30:27.129335000Z][com.docker.diagnose][W] (13c815ca-7) cc0da2a6-diagnose-network C<-S NoResponse GET /ping (1.170792ms): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory
[2022-10-20T22:30:28.130231000Z][com.docker.diagnose][I] (13c815ca-8) cc0da2a6-diagnose-network C->S diagnosticsd GET /ping
[2022-10-20T22:30:28.131362000Z][com.docker.diagnose][W] (13c815ca-8) cc0da2a6-diagnose-network C<-S NoResponse GET /ping (1.126125ms): 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 1 issue:

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.

Steps to reproduce the behavior

1. Run out of disk space
2. Try to move your container storage to another drive
3. Kill Docker when it fails
4. Now you're doomed

[timmattison]

This is the same issue as #6190 which doesn't have any other answers

[timmattison]

The only solution I've found is to nuke everything like this:

sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/docker

Then restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.

Unfortunately I still can't move my disk image storage to another drive but that's something for another day.

[spencerbeggs]

@timmattison Thank you. This worked for me after Docker stopped working after I upgraded to Ventura.

[dhanyn10]

The only solution I've found is to nuke everything like this:

sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/docker

Then restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.

Unfortunately I still can't move my disk image storage to another drive but that's something for another day.

after updating several things in linux mint 21 listed in update manager, my docker stopped working, and when i've tried reinstalling even with different version, it's not working too. But, thanks to this answer my docker working again.

[bazerama]

The only solution I've found is to nuke everything like this:

sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/docker

Then restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.

Unfortunately I still can't move my disk image storage to another drive but that's something for another day.

Had this problem on M2 Apple Silicon Mac running Monterey 12.5.1, this fixed it, not sure why it was messed in the first place :(

[jsolderitsch]

@timmattison suggestion worked for me. I had previously gotten a bad update experience and re-installed 4.12. This worked for awhile but I got nagged again to update to 4.13.1 and decided to try the update. It seemed to leave 4.13.1 installed but it did not run when I clicked on the Docker Desktop application icon. I saw some dormant docker processes using Activity Monitor and killed them. I trashed the updated version, freshly installed 4.13.1 using the .dmg file and it still didn't start -- same dormant docker process seen with Activity Monitor, which I killed. Then I nuked everything via the sudo command and then the freshly installed 4.13.1 did come up as expected. I am running Monterey on an Intel Mac. The update process needs some reviewing on the part of the Docker Desktop Dev team for Mac.
I don't see the Fatal Error Exit Status 1 message at all. I see no errors -- docker desktop just fails to appear. Until I ran the sudo clean out command.

[preston-m-price]

@timmattison's suggestion unblocked me as well after I upgraded to Mac OS v 13.0/Ventura. Thanks!

[shadda]

I can't get it working. I restored from time machine and that completely hosed it. I've nuked every related file multiple times and it just gives me exit status 1.

[MateuszBednarczyk]

Same issue. I've changed the default containers path to the external device and it's crashing now.

[akshaypansari]

#6499
The above command didn't work. This thread solution worked for me

[derekpierre]

The only solution I've found is to nuke everything like this:

sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/docker

This also got me back up and running (on MacOS Ventura).

Apologies to the Docker Team in advance, but the upgrade installation is not reliable. I have to uninstall everything caches etc … many times before installing a new version otherwise, I’m in for a lot of pain. This way, it usually works.

[Vsion]

The only solution I've found is to nuke everything like this:

sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/docker

Then restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.

Unfortunately I still can't move my disk image storage to another drive but that's something for another day.

it works ! thanks