docker
Docker Desktop is not starting
Description
Docker Desktop is not starting. I tried multiple things without success:
- reinstall
- install from brew
- purge all data
- downgrade to older version (for example 4.18 or 4.24)
- even colima is not starting
Screenshots:
What may be also interesting docker command is not found immediately:
docker
zsh: command not found: docker
When add it to PATH:
export PATH="/Applications/Docker.app/Contents/Resources/bin:$PATH"
then docker command is available but:
docker info
Client:
Version: 26.1.4
Context: desktop-linux
Debug Mode: false
Server:
ERROR: Cannot connect to the Docker daemon at unix:///Users/dunix/.docker/run/docker.sock. Is the docker daemon running?
errors pretty printing info
As I mentioned I tried almost everything without result :(
Reproduce
- Download Docker Desktop
- Install it
- Application is not loading
Expected behavior
Docker Desktop should successfully start up
docker version
Client:
Version: 26.1.4
API version: 1.45
Go version: go1.21.11
Git commit: 5650f9b
Built: Wed Jun 5 11:26:02 2024
OS/Arch: darwin/arm64
Context: desktop-linux
Cannot connect to the Docker daemon at unix:///Users/dunix/.docker/run/docker.sock. Is the docker daemon running?
docker info
Client:
Version: 26.1.4
Context: desktop-linux
Debug Mode: false
Server:
ERROR: Cannot connect to the Docker daemon at unix:///Users/dunix/.docker/run/docker.sock. Is the docker daemon running?
errors pretty printing info
Diagnostics ID
F2C214D0-FA18-49B5-BA59-97A48DC0ACA3/20240710070332
Additional Info
No response
me too I also tried most of the above on my mac and it wont load at all. its weird it happened after a restart last night.
(base) john@JohnsMacStudio ~ % /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check Starting diagnostics
[2024-07-12T15:21:55.160270000Z][com.docker.diagnose.ipc] 64acf2c7-diagnose -> <HOME>/Library/Containers/com.docker.docker/Data/backend.sock BackendAPI [2024-07-12T15:21:55.160872000Z][com.docker.diagnose.ipc] (d877d46a) 64acf2c7-diagnose C->S BackendAPI POST /idle/make-busy [2024-07-12T15:21:55.163262000Z][com.docker.diagnose.ipc][W] (d877d46a) 64acf2c7-diagnose C<-S NoResponse POST /idle/make-busy (2.385875ms): Post "http://ipc/idle/make-busy": dial unix <HOME>/Library/Containers/com.docker.docker/Data/backend.sock: connect: no such file or directory [2024-07-12T15:21:56.161765000Z][com.docker.diagnose.ipc] (a35142a7) 64acf2c7-diagnose C->S BackendAPI GET /idle [2024-07-12T15:21:56.164567000Z][com.docker.diagnose.ipc][W] (a35142a7) 64acf2c7-diagnose C<-S NoResponse GET /idle (2.8215ms): Get "http://ipc/idle": dial unix <HOME>/Library/Containers/com.docker.docker/Data/backend.sock: connect: no such file or directory [PASS] DD0027: is there available disk space on the host? [FAIL] DD0028: is there available VM disk space? open /Users/john/Library/Group Containers/group.com.docker/settings.json: no such file or directory [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [FAIL] DD0017: can a VM be started? vm has not started: failed to open init.log: open log/vm/console.log: no such file or directory [FAIL] DD0016: is the LinuxKit VM running? prereq failed: can a VM be started? [FAIL] DD0004: is the Docker engine running? prereq failed: is the LinuxKit VM running? [FAIL] DD0015: are the binary symlinks installed? checking binaries in /usr/local/bin: looking for /usr/local/bin/docker: lstat /usr/local/bin/docker: no such file or directory checking binaries in $HOME/.docker/bin: unable to find /Users/john/.docker/bin: stat /Users/john/.docker/bin: no such file or directory [FAIL] DD0031: does the Docker API work? prereq failed: is the Docker engine running? [FAIL] DD0013: is the $PATH ok? unable to find docker executable on PATH [FAIL] DD0003: is the Docker CLI working? prereq failed: is the Docker engine running? [FAIL] DD0038: is the connection to Docker working? prereq failed: is the Docker engine running? [FAIL] DD0014: are the backend processes running? prereq failed: is the LinuxKit VM running? [FAIL] DD0007: is the backend responding? prereq failed: are the backend processes running? [FAIL] DD0009: is the vpnkit API responding? prereq failed: are the backend processes running? [FAIL] DD0010: is the Docker API proxy responding? prereq failed: are the backend processes running? [FAIL] DD0030: is the image access management authorized? prereq failed: is the Docker engine running? [PASS] DD0033: does the host have Internet access? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [WARN] DD0017: can a VM be started? vm has not started: failed to open init.log: open log/vm/console.log: no such file or directory [WARN] DD0016: is the LinuxKit VM running? prereq failed: can a VM be started? [WARN] DD0004: is the Docker engine running? prereq failed: is the LinuxKit VM running? [WARN] DD0015: are the binary symlinks installed? checking binaries in /usr/local/bin: looking for /usr/local/bin/docker: lstat /usr/local/bin/docker: no such file or directory checking binaries in $HOME/.docker/bin: unable to find /Users/john/.docker/bin: stat /Users/john/.docker/bin: no such file or directory [WARN] DD0031: does the Docker API work? prereq failed: is the Docker engine running? [WARN] DD0032: do Docker networks overlap with host IPs? prereq failed: does the Docker API work?
Please note the following 6 warnings:
1 : The check: can a VM be started? Produced the following warning: vm has not started: failed to open init.log: open log/vm/console.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 check: is the LinuxKit VM running? Produced the following warning: prereq failed: can a VM be started?
The Docker engine runs inside a Linux VM. Therefore the VM must be running.
3 : The check: is the Docker engine running? Produced the following warning: prereq failed: is the LinuxKit VM running?
The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.
4 : The check: are the binary symlinks installed? Produced the following warning: checking binaries in /usr/local/bin: looking for /usr/local/bin/docker: lstat /usr/local/bin/docker: no such file or directory checking binaries in $HOME/.docker/bin: unable to find /Users/john/.docker/bin: stat /Users/john/.docker/bin: no such file or directory
The symlinks to the docker CLI etc are needed for docker commands to work.
5 : The check: does the Docker API work? Produced the following warning: prereq failed: is the Docker engine running?
If the Docker API is not available from the host then Docker Desktop will not work correctly.
6 : The check: do Docker networks overlap with host IPs? Produced the following warning: prereq failed: does the Docker API work?
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 4 issues:
1 : The test: are the binary symlinks installed? Failed with: checking binaries in /usr/local/bin: looking for /usr/local/bin/docker: lstat /usr/local/bin/docker: no such file or directory checking binaries in $HOME/.docker/bin: unable to find /Users/john/.docker/bin: stat /Users/john/.docker/bin: no such file or directory
The symlinks to the docker CLI etc are needed for docker commands to work.
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: is there available VM disk space? Failed with: open /Users/john/Library/Group Containers/group.com.docker/settings.json: no such file or directory
Verify the available VM disk space. Try running docker system prune to clean up.
4 : The test: can a VM be started? Failed with: vm has not started: failed to open init.log: open log/vm/console.log: no such file or directory
The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.
Ive tried reinstalling docker and Mac os still wont load.
At some point 5-10 weeks back I upgraded docker and it broke. Now infinitely hangs. Completely unusable.
Diaognostic:
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Starting diagnostics
[2024-08-07T16:51:22.304451000Z][com.docker.diagnose.ipc] 37d4acc8-diagnose -> <HOME>/Library/Containers/com.docker.docker/Data/backend.sock BackendAPI
[2024-08-07T16:51:22.305684000Z][com.docker.diagnose.ipc] (a73105a0) 37d4acc8-diagnose C->S BackendAPI POST /idle/make-busy
[2024-08-07T16:51:22.306345000Z][com.docker.diagnose.ipc] (a73105a0) 37d4acc8-diagnose C<-S f09995b8-BackendAPI POST /idle/make-busy (656.083µs): 0x1400013e3d0
[2024-08-07T16:51:23.305843000Z][com.docker.diagnose.ipc] (e2d881b6) 37d4acc8-diagnose C->S BackendAPI GET /idle
[2024-08-07T16:51:23.307076000Z][com.docker.diagnose.ipc] (e2d881b6) 37d4acc8-diagnose C<-S f09995b8-BackendAPI GET /idle (1.187083ms): {"apisInFlight":{"/_ping":5},"booted":false,"busyReason":["in-flight APIs: map[/_ping:5]","timed activities: map[/idle/make-busy:28.999618417s]"],"containers":0,"idle":"bool","kubernetesEnabled":false,"reduced":false,"services":0,"timedActivities":{"/idle/make-busy":"float64"},"vmPaused":false,"vmRunning":true,"vmStopped":false,"windowsContainers":false}
[PASS] DD0027: is there available disk space on the host?
[PASS] 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] DD0004: is the Docker engine running? Cannot connect to the Docker daemon at unix:///Users/michaelmentele/Library/Containers/com.docker.docker/Data/docker.raw.sock. Is the docker daemon running?
[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? prereq failed: is the Docker engine running?
[FAIL] DD0013: is the $PATH ok? unable to find docker executable on PATH
[FAIL] DD0003: is the Docker CLI working? prereq failed: is the Docker engine running?
[FAIL] DD0038: is the connection to Docker working? prereq failed: is the Docker engine running?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[SKIP] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[FAIL] DD0030: is the image access management authorized? prereq failed: is the Docker engine running?
[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] DD0004: is the Docker engine running? Cannot connect to the Docker daemon at unix:///Users/michaelmentele/Library/Containers/com.docker.docker/Data/docker.raw.sock. Is the docker daemon running?
[PASS] DD0015: are the binary symlinks installed?
[WARN] DD0031: does the Docker API work? prereq failed: is the Docker engine running?
[WARN] DD0032: do Docker networks overlap with host IPs? prereq failed: does the Docker API work?
Please note the following 3 warnings:
1 : The check: is the Docker engine running?
Produced the following warning: Cannot connect to the Docker daemon at unix:///Users/michaelmentele/Library/Containers/com.docker.docker/Data/docker.raw.sock. Is the docker daemon running?
The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.
2 : The check: does the Docker API work?
Produced the following warning: prereq failed: is the Docker engine running?
If the Docker API is not available from the host then Docker Desktop will not work correctly.
3 : The check: do Docker networks overlap with host IPs?
Produced the following warning: prereq failed: does the Docker API work?
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: is the Docker engine running?
Failed with: Cannot connect to the Docker daemon at unix:///Users/michaelmentele/Library/Containers/com.docker.docker/Data/docker.raw.sock. Is the docker daemon running?
The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.
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
The app launches but the engine just won't start for some reason. I uninstalled and reinstalled with brew install --cask docker and now I get:
Which is odd since this previously worked on this macbook.
Maybe the brew install doesn't use apple silicon build.
Uninstalling seems to have worked for me 🎉 https://docs.docker.com/desktop/uninstall/