docker / for-mac

Bug reports for Docker Desktop for Mac
https://www.docker.com/products/docker#/mac
2.43k stars 117 forks source link

Docker 4.19.0 does not start up on macOS Ventura 13.0 #6830

Open aareki opened 1 year ago

aareki commented 1 year ago

I have tried the latest version of Docker Desktop I have uploaded Diagnostics Diagnostics ID: 2023-05-08T15:20:11.536393000Z

Expected behavior

After attempting to start Docker Desktop for macOS Ventura, I can see Docker Desktop in the macOS menu bar and a Fatal Error message is popping up. I clicked Reset Docker to factory defaults and Docker Desktop is closed and disappeared from the menu bar.

Actual behavior

After attempting to start Docker Desktop for macOS Ventura, nothing happens.

Information

This issue is reproducible.
The problem is on my new laptop
    macOS Version: Ventura 13.0
    Intel chip or Apple chip: Apple
    Docker Desktop Version: 4.19.0

Output of: /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check

[2023-05-08T15:20:11.536393000Z][com.docker.diagnose][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[SKIP] 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: connection refused
[2023-05-08T15:20:11.572218000Z][com.docker.diagnose][I] ipc.NewClient: fa9eedb3-diagnose -> diagnosticd.sock diagnosticsd
[2023-05-08T15:20:11.572431000Z][com.docker.diagnose][I] (f79afb1b) fa9eedb3-diagnose C->S diagnosticsd GET /ping
[2023-05-08T15:20:11.573779000Z][com.docker.diagnose][W] (f79afb1b) fa9eedb3-diagnose C<-S NoResponse GET /ping (1.322833ms): Get "http://ipc/ping": dial unix diagnosticd.sock: connect: connection refused

[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: connection refused
[2023-05-08T15:20:11.574096000Z][com.docker.diagnose][I] ipc.NewClient: e557c5f8-com.docker.diagnose -> lifecycle-server.sock VMDockerdAPI
[2023-05-08T15:20:11.574253000Z][com.docker.diagnose][I] (9cfa2a89) e557c5f8-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-05-08T15:20:11.574712000Z][com.docker.diagnose][W] (9cfa2a89) e557c5f8-com.docker.diagnose C<-S NoResponse GET /docker (456.292µs): Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: connection refused
[2023-05-08T15:20:11.574924000Z][com.docker.diagnose][I] (9cfa2a89-1) e557c5f8-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-08T15:20:11.575451000Z][com.docker.diagnose][W] (9cfa2a89-1) e557c5f8-com.docker.diagnose C<-S NoResponse GET /ping (522.125µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: connection refused
[2023-05-08T15:20:12.575902000Z][com.docker.diagnose][I] (9cfa2a89-2) e557c5f8-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-08T15:20:12.577625000Z][com.docker.diagnose][W] (9cfa2a89-2) e557c5f8-com.docker.diagnose C<-S NoResponse GET /ping (1.723334ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: connection refused
[2023-05-08T15:20:13.578389000Z][com.docker.diagnose][I] (9cfa2a89-3) e557c5f8-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-08T15:20:13.580562000Z][com.docker.diagnose][W] (9cfa2a89-3) e557c5f8-com.docker.diagnose C<-S NoResponse GET /ping (2.165084ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: connection refused
[2023-05-08T15:20:14.581874000Z][com.docker.diagnose][I] (9cfa2a89-4) e557c5f8-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-08T15:20:14.584018000Z][com.docker.diagnose][W] (9cfa2a89-4) e557c5f8-com.docker.diagnose C<-S NoResponse GET /ping (2.134417ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: connection refused
[2023-05-08T15:20:15.585274000Z][com.docker.diagnose][I] (9cfa2a89-5) e557c5f8-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-08T15:20:15.587318000Z][com.docker.diagnose][W] (9cfa2a89-5) e557c5f8-com.docker.diagnose C<-S NoResponse GET /ping (2.013042ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: connection refused
[2023-05-08T15:20:16.588583000Z][com.docker.diagnose][I] (9cfa2a89-6) e557c5f8-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-08T15:20:16.590717000Z][com.docker.diagnose][W] (9cfa2a89-6) e557c5f8-com.docker.diagnose C<-S NoResponse GET /ping (2.117125ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: connection refused
[2023-05-08T15:20:17.591981000Z][com.docker.diagnose][I] (9cfa2a89-7) e557c5f8-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-08T15:20:17.594065000Z][com.docker.diagnose][W] (9cfa2a89-7) e557c5f8-com.docker.diagnose C<-S NoResponse GET /ping (2.075208ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: connection refused
[2023-05-08T15:20:18.595399000Z][com.docker.diagnose][I] (9cfa2a89-8) e557c5f8-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-08T15:20:18.597501000Z][com.docker.diagnose][W] (9cfa2a89-8) e557c5f8-com.docker.diagnose C<-S NoResponse GET /ping (2.0935ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: connection refused

[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?
[FAIL] DD0013: is the $PATH ok? unable to find docker executable on PATH
[FAIL] DD0003: is the Docker CLI working? exec: "docker": executable file not found in $PATH
[PASS] DD0038: is the connection to Docker working?
[FAIL] DD0014: are the backend processes running? 3 errors occurred:
    * com.docker.vpnkit is not running
    * com.docker.driver.amd64-linux is not running
    * qemu-system-aarch64 is not running

[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[FAIL] DD0009: is the vpnkit API responding? dial unix vpnkit.diag.sock: connect: no such file or directory
[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/aareki/.docker/run/docker.sock: connect: connection refused
[2023-05-08T15:20:19.434289000Z][com.docker.diagnose][I] ipc.NewClient: 9fb002f9-diagnose -> <HOME>/.docker/run/docker.sock Proxy
[2023-05-08T15:20:19.434501000Z][com.docker.diagnose][I] (fe986f28) 9fb002f9-diagnose C->S Proxy GET /desktop-diagnostics/ping
[2023-05-08T15:20:19.434860000Z][com.docker.diagnose][W] (fe986f28) 9fb002f9-diagnose C<-S NoResponse GET /desktop-diagnostics/ping (355.708µs): Get "http://ipc/desktop-diagnostics/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-08T15:20:19.435151000Z][com.docker.diagnose][I] (fe986f28-1) 9fb002f9-diagnose C->S Proxy GET /ping
[2023-05-08T15:20:19.435453000Z][com.docker.diagnose][W] (fe986f28-1) 9fb002f9-diagnose C<-S NoResponse GET /ping (300.166µs): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-08T15:20:20.436279000Z][com.docker.diagnose][I] (fe986f28-2) 9fb002f9-diagnose C->S Proxy GET /ping
[2023-05-08T15:20:20.438404000Z][com.docker.diagnose][W] (fe986f28-2) 9fb002f9-diagnose C<-S NoResponse GET /ping (2.108458ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-08T15:20:21.439645000Z][com.docker.diagnose][I] (fe986f28-3) 9fb002f9-diagnose C->S Proxy GET /ping
[2023-05-08T15:20:21.441544000Z][com.docker.diagnose][W] (fe986f28-3) 9fb002f9-diagnose C<-S NoResponse GET /ping (1.889417ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-08T15:20:22.442534000Z][com.docker.diagnose][I] (fe986f28-4) 9fb002f9-diagnose C->S Proxy GET /ping
[2023-05-08T15:20:22.444571000Z][com.docker.diagnose][W] (fe986f28-4) 9fb002f9-diagnose C<-S NoResponse GET /ping (2.021792ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-08T15:20:23.445946000Z][com.docker.diagnose][I] (fe986f28-5) 9fb002f9-diagnose C->S Proxy GET /ping
[2023-05-08T15:20:23.447959000Z][com.docker.diagnose][W] (fe986f28-5) 9fb002f9-diagnose C<-S NoResponse GET /ping (2.003166ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-08T15:20:24.449220000Z][com.docker.diagnose][I] (fe986f28-6) 9fb002f9-diagnose C->S Proxy GET /ping
[2023-05-08T15:20:24.452379000Z][com.docker.diagnose][W] (fe986f28-6) 9fb002f9-diagnose C<-S NoResponse GET /ping (3.141ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-08T15:20:25.454546000Z][com.docker.diagnose][I] (fe986f28-7) 9fb002f9-diagnose C->S Proxy GET /ping
[2023-05-08T15:20:25.457019000Z][com.docker.diagnose][W] (fe986f28-7) 9fb002f9-diagnose C<-S NoResponse GET /ping (2.456959ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-08T15:20:26.457812000Z][com.docker.diagnose][I] (fe986f28-8) 9fb002f9-diagnose C->S Proxy GET /ping
[2023-05-08T15:20:26.460003000Z][com.docker.diagnose][W] (fe986f28-8) 9fb002f9-diagnose C<-S NoResponse GET /ping (2.170666ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused

[SKIP] DD0030: is the image access management authorized?
[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?
[WARN] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": dial unix diagnosticd.sock: connect: connection refused
[WARN] DD0004: is the Docker engine running? Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: connection refused
[PASS] DD0015: are the binary symlinks installed?
[WARN] DD0031: does the Docker API work? Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?
[WARN] DD0032: do Docker networks overlap with host IPs? Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?

Please note the following 4 warnings:

1 : The check: are the LinuxKit services running?
    Produced the following warning: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": dial unix diagnosticd.sock: connect: connection refused

The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.

2 : The check: is the Docker engine running?
    Produced the following warning: Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: connection refused

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

3 : The check: does the Docker API work?
    Produced the following warning: Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?

If the Docker API is not available from the host then Docker Desktop will not work correctly.

4 : The check: do Docker networks overlap with host IPs?
    Produced the following warning: Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address

Please investigate the following 3 issues:

1 : The test: are the LinuxKit services running?
    Failed with: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": dial unix diagnosticd.sock: connect: connection refused

The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.

2 : The test: is the $PATH ok?
    Failed with: unable to find docker executable on PATH

The directory containing the docker CLI tools must be on the $PATH

3 : The test: are the backend processes running?
    Failed with: 3 errors occurred:
    * com.docker.vpnkit is not running
    * com.docker.driver.amd64-linux is not running
    * qemu-system-aarch64 is not running

Not all of the backend processes are running.
rcontreras-te commented 1 year ago

Seeing the same thing. After upgrading Docker Desktop doesn't want to start.

macOS: Ventura 13.3.1 (a) - M1 Docker Desktop: 4.18.0 (104112)

Same as #6829

cougarsyankeesfan commented 1 year ago

Completely uninstalling Docker Desktop, rebooting, and reinstalling it on my Mac M1 fixed it for me. https://docs.docker.com/desktop/uninstall/

bodom0015 commented 1 year ago

Possibly unrelated, but I recently upgraded to macOS 13.3.1 (a) and Docker Desktop 4.19.0. I have an Intel Mac (not M1) and I have buildkit enabled, if that matters as well.

Although my Docker Desktop did not fail to start, I was seeing very odd performance issues while building a handful of specific images. These are typical Angular applications with fairly standard practices that had built successfully prior to upgrading Docker.

I can confirm that uninstalling Docker Desktop and then reinstalling it fixed the issues that I was seeing. Thank you, @cougarsyankeesfan for the suggestion! :tada:

Verbose details: During the Docker build, we are running npm install to fetch dependencies. This was failing to fetch basic Angular dependencies, such as @angular-devkit/build-angular. Turning on verbose logging we could confirm that many dependencies of the application's were installing correctly, but a couple of them were reporting timeouts after ~1000s had passed:

#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@typescript-eslint/utils/node_modules/semver 1683902164197
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@typescript-eslint/typescript-estree 1683902164197
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@typescript-eslint/typescript-estree/node_modules/semver 1683902164197
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@typescript-eslint/experimental-utils/node_modules/semver 1683902164197
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@typescript-eslint/experimental-utils/node_modules/@typescript-eslint/scope-manager 1683902164197
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@typescript-eslint/eslint-plugin/node_modules/semver 1683902164197
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@types/json-schema 1683902164198
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@types/express 1683902164198
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@nuxtjs/opencollective 1683902164198
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@jridgewell/trace-mapping 1683902164199
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@jridgewell/set-array 1683902164199
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/types 1683902164200
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/plugin-transform-regenerator 1683902164200
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/plugin-transform-parameters 1683902164200
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/plugin-transform-new-target 1683902164200
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/plugin-transform-exponentiation-operator 1683902164200
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/plugin-transform-block-scoping 1683902164201
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/plugin-syntax-top-level-await 1683902164201
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/plugin-syntax-dynamic-import 1683902164201
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/plugin-proposal-class-properties 1683902164201
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/helper-string-parser 1683902164201
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/helper-skip-transparent-expression-wrappers 1683902164201
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@babel/helper-module-transforms 1683902164202
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@angular/compiler-cli 1683902164203
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@angular/cdk 1683902164204
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@angular/animations 1683902164204
#0 991.9 npm verb unfinished npm timer reifyNode:node_modules/@angular-devkit/core 1683902164204
#0 991.9 npm verb code 1
#0 991.9 
#0 991.9 npm ERR! A complete log of this run can be found in:
#0 991.9 npm ERR!     /root/.npm/_logs/2023-05-12T14_36_02_455Z-debug-0.log
------
failed to solve: process "/bin/sh -c npm install --loglevel=verbose" did not complete successfully: exit code: 1

So if Docker Desktop does start up properly under these versions, then it would appear that it can sometimes have degraded network or volume performance during docker build as a symptom as well. I was unable to determine if the bottleneck was the download speed or the volume write speed, but figured I would share this analysis in case it might be helpful.

Uninstalling Docker Desktop and reinstalling it, per the suggestion above fixed the issue for me. And now the full image build completes in under 2 minutes using --no-cache 🎉 🎊

aareki commented 1 year ago

thanks all for the comment. Actually one of our tech support helped me to fix this. He told me to run the following script and it fixed the issue.

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

maxvisser commented 1 year ago

Same problem here, @aareki script works to fix the issue. Needed to kill com.docker.backend in activity monitor and start docker.

next day after reboot same problem, again used the script to fix the issue. If it keeps returning I will need to look into downgrading