search

docker / for-mac

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

Docker installation failure #6858

Open tilwinjoy opened 1 year ago

tilwinjoy commented 1 year ago

Expected behavior

Docker installation succeeds without errors

Actual behavior

Installation fails on the recommended/advanced settings step with partially visible error message

Screenshot 2023-05-29 at 17 03 56

Information

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

/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
[2023-05-29T07:10:18.815296000Z][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: no such file or directory
[2023-05-29T07:10:18.863463000Z][com.docker.diagnose][I] ipc.NewClient: 5efaf3ec-diagnose -> diagnosticd.sock diagnosticsd
[2023-05-29T07:10:18.863824000Z][com.docker.diagnose][I] (6e2e7458) 5efaf3ec-diagnose C->S diagnosticsd GET /ping
[2023-05-29T07:10:18.865245000Z][com.docker.diagnose][W] (6e2e7458) 5efaf3ec-diagnose C<-S NoResponse GET /ping (1.402824ms): 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
[2023-05-29T07:10:18.866417000Z][com.docker.diagnose][I] ipc.NewClient: f5c05080-com.docker.diagnose -> lifecycle-server.sock VMDockerdAPI
[2023-05-29T07:10:18.866730000Z][com.docker.diagnose][I] (d7b2e165) f5c05080-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-05-29T07:10:18.867288000Z][com.docker.diagnose][W] (d7b2e165) f5c05080-com.docker.diagnose C<-S NoResponse GET /docker (554.291µs): Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-05-29T07:10:18.867644000Z][com.docker.diagnose][I] (d7b2e165-1) f5c05080-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-29T07:10:18.868031000Z][com.docker.diagnose][W] (d7b2e165-1) f5c05080-com.docker.diagnose C<-S NoResponse GET /ping (380.773µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-05-29T07:10:19.869222000Z][com.docker.diagnose][I] (d7b2e165-2) f5c05080-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-29T07:10:19.870079000Z][com.docker.diagnose][W] (d7b2e165-2) f5c05080-com.docker.diagnose C<-S NoResponse GET /ping (852.713µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-05-29T07:10:20.870610000Z][com.docker.diagnose][I] (d7b2e165-3) f5c05080-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-29T07:10:20.871562000Z][com.docker.diagnose][W] (d7b2e165-3) f5c05080-com.docker.diagnose C<-S NoResponse GET /ping (945.432µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-05-29T07:10:21.872349000Z][com.docker.diagnose][I] (d7b2e165-4) f5c05080-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-29T07:10:21.873313000Z][com.docker.diagnose][W] (d7b2e165-4) f5c05080-com.docker.diagnose C<-S NoResponse GET /ping (957.826µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-05-29T07:10:22.875107000Z][com.docker.diagnose][I] (d7b2e165-5) f5c05080-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-29T07:10:22.875914000Z][com.docker.diagnose][W] (d7b2e165-5) f5c05080-com.docker.diagnose C<-S NoResponse GET /ping (802.126µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-05-29T07:10:23.876512000Z][com.docker.diagnose][I] (d7b2e165-6) f5c05080-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-29T07:10:23.877492000Z][com.docker.diagnose][W] (d7b2e165-6) f5c05080-com.docker.diagnose C<-S NoResponse GET /ping (987.508µs): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-05-29T07:10:24.878176000Z][com.docker.diagnose][I] (d7b2e165-7) f5c05080-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-29T07:10:24.879469000Z][com.docker.diagnose][W] (d7b2e165-7) f5c05080-com.docker.diagnose C<-S NoResponse GET /ping (1.289101ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory
[2023-05-29T07:10:25.880135000Z][com.docker.diagnose][I] (d7b2e165-8) f5c05080-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-29T07:10:25.881412000Z][com.docker.diagnose][W] (d7b2e165-8) f5c05080-com.docker.diagnose C<-S NoResponse GET /ping (1.274753ms): Get "http://ipc/ping": dial unix lifecycle-server.sock: connect: no such file or directory

[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?
[PASS] DD0013: is the $PATH ok?
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] 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
    * com.docker.virtualization 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: 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/tjoy/.docker/run/docker.sock: connect: connection refused
[2023-05-29T07:10:28.077487000Z][com.docker.diagnose][I] ipc.NewClient: 51ce7757-diagnose -> <HOME>/.docker/run/docker.sock Proxy
[2023-05-29T07:10:28.077857000Z][com.docker.diagnose][I] (6260bc49) 51ce7757-diagnose C->S Proxy GET /desktop-diagnostics/ping
[2023-05-29T07:10:28.078304000Z][com.docker.diagnose][W] (6260bc49) 51ce7757-diagnose C<-S NoResponse GET /desktop-diagnostics/ping (437.474µs): Get "http://ipc/desktop-diagnostics/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-29T07:10:28.078747000Z][com.docker.diagnose][I] (6260bc49-1) 51ce7757-diagnose C->S Proxy GET /ping
[2023-05-29T07:10:28.079186000Z][com.docker.diagnose][W] (6260bc49-1) 51ce7757-diagnose C<-S NoResponse GET /ping (435.291µs): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-29T07:10:29.080389000Z][com.docker.diagnose][I] (6260bc49-2) 51ce7757-diagnose C->S Proxy GET /ping
[2023-05-29T07:10:29.081067000Z][com.docker.diagnose][W] (6260bc49-2) 51ce7757-diagnose C<-S NoResponse GET /ping (670.564µs): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-29T07:10:30.082543000Z][com.docker.diagnose][I] (6260bc49-3) 51ce7757-diagnose C->S Proxy GET /ping
[2023-05-29T07:10:30.096104000Z][com.docker.diagnose][W] (6260bc49-3) 51ce7757-diagnose C<-S NoResponse GET /ping (13.553575ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-29T07:10:31.096944000Z][com.docker.diagnose][I] (6260bc49-4) 51ce7757-diagnose C->S Proxy GET /ping
[2023-05-29T07:10:31.098152000Z][com.docker.diagnose][W] (6260bc49-4) 51ce7757-diagnose C<-S NoResponse GET /ping (1.203231ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-29T07:10:32.098584000Z][com.docker.diagnose][I] (6260bc49-5) 51ce7757-diagnose C->S Proxy GET /ping
[2023-05-29T07:10:32.099521000Z][com.docker.diagnose][W] (6260bc49-5) 51ce7757-diagnose C<-S NoResponse GET /ping (929.741µs): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-29T07:10:33.101147000Z][com.docker.diagnose][I] (6260bc49-6) 51ce7757-diagnose C->S Proxy GET /ping
[2023-05-29T07:10:33.102316000Z][com.docker.diagnose][W] (6260bc49-6) 51ce7757-diagnose C<-S NoResponse GET /ping (1.169396ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-29T07:10:34.103753000Z][com.docker.diagnose][I] (6260bc49-7) 51ce7757-diagnose C->S Proxy GET /ping
[2023-05-29T07:10:34.105029000Z][com.docker.diagnose][W] (6260bc49-7) 51ce7757-diagnose C<-S NoResponse GET /ping (1.272473ms): Get "http://ipc/ping": dial unix <HOME>/.docker/run/docker.sock: connect: connection refused
[2023-05-29T07:10:35.106321000Z][com.docker.diagnose][I] (6260bc49-8) 51ce7757-diagnose C->S Proxy GET /ping
[2023-05-29T07:10:35.106960000Z][com.docker.diagnose][W] (6260bc49-8) 51ce7757-diagnose C<-S NoResponse GET /ping (636.375µs): 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: no such file or directory
[WARN] DD0004: is the Docker engine running? Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory
[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: no such file or directory

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: no such file or directory

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 2 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: no such file or directory

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

2 : 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
    * com.docker.virtualization is not running

Not all of the backend processes are running.

Steps to reproduce the behavior

  1. Download Docker from https://docs.docker.com/desktop/install/mac-install/#install-and-run-docker-desktop-on-mac
  2. Double click the downloaded file and follow instructions
kreyken1900 commented 1 year ago

After trying many install process, I luckily was able to see that a file permissions issues was causing the problem. This worked: sudo /Applications/Docker.app/Contents/MacOS/install --accept-license And Docker started working fine.

tilwinjoy commented 1 year ago

Would be awesome if the error message was more visible/mentioned that this is permission related issue!

chobbs- commented 1 year ago

Just had this same issue after installing Docker v4.20.1 through Homebrew. The fix mentioned by @kreyken1900 worked luckily.