You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[2025-01-08T16:18:18.164578000Z][com.docker.diagnose.ipc] 658bf048-diagnose -> /Library/Containers/com.docker.docker/Data/backend.sock BackendAPI
[2025-01-08T16:18:18.169212000Z][com.docker.diagnose.ipc] (b598f0f5-0) 658bf048-diagnose C->S BackendAPI POST /idle/make-busy
[2025-01-08T16:18:18.169990000Z][com.docker.diagnose.ipc][W] (b598f0f5-0) 658bf048-diagnose C<-S ConnectionClosed POST /idle/make-busy (776.792µs): Post "http://ipc/idle/make-busy": dial unix /Library/Containers/com.docker.docker/Data/backend.sock: connect: no such file or directory
[2025-01-08T16:18:19.170433000Z][com.docker.diagnose.ipc] (b598f0f5-3) 658bf048-diagnose C->S BackendAPI GET /idle
[2025-01-08T16:18:19.172700000Z][com.docker.diagnose.ipc][W] (b598f0f5-3) 658bf048-diagnose C<-S ConnectionClosed GET /idle (2.266542ms): Get "http://ipc/idle": dial unix /Library/Containers/com.docker.docker/Data/backend.sock: connect: no such file or directory
[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?
[FAIL] DD0017: can a VM be started? vm has not started: failed to open init.log: open /Users/majha/Library/Containers/com.docker.docker/Data/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?
[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? prereq failed: is the Docker engine running?
[PASS] DD0013: is the $PATH ok?
[FAIL] DD0003: is the Docker CLI working? prereq failed: is the Docker engine running?
[FAIL] DD0037: 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] 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 /Users/majha/Library/Containers/com.docker.docker/Data/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?
[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 5 warnings:
1 : The check: can a VM be started?
Produced the following warning: vm has not started: failed to open init.log: open /Users/majha/Library/Containers/com.docker.docker/Data/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: 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.
5 : 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.
1 : The test: can a VM be started?
Failed with: vm has not started: failed to open init.log: open /Users/majha/Library/Containers/com.docker.docker/Data/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.
Reproduce
Download docker.dmg from docker official website.
Install docker to applications.
Restart system.
Try running by clicking on the docker application icon.
Expected behavior
Docker desktop application opens.
docker version
Docker version 27.4.1, build b9d17eaebb
docker info
% docker info
Client: Docker Engine - Community
Version: 27.4.1
Context: default
Debug Mode: false
Plugins:
ai: Ask Gordon - Docker Agent (Docker Inc.)
Version: v0.5.1
Path: /Users/majha/.docker/cli-plugins/docker-ai
buildx: Docker Buildx (Docker Inc.)
Version: v0.19.2-desktop.1
Path: /Users/majha/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.31.0-desktop.2
Path: /Users/majha/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.37
Path: /Users/majha/.docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Beta) (Docker Inc.)
Version: v0.1.0
Path: /Users/majha/.docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /Users/majha/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.27
Path: /Users/majha/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: /Users/majha/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: /Users/majha/.docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /Users/majha/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.15.1
Path: /Users/majha/.docker/cli-plugins/docker-scout
Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info
Description
Docker not running after installing Docker desktop for Mac.
% /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Starting diagnostics
[2025-01-08T16:18:18.164578000Z][com.docker.diagnose.ipc] 658bf048-diagnose -> /Library/Containers/com.docker.docker/Data/backend.sock BackendAPI
[2025-01-08T16:18:18.169212000Z][com.docker.diagnose.ipc] (b598f0f5-0) 658bf048-diagnose C->S BackendAPI POST /idle/make-busy
[2025-01-08T16:18:18.169990000Z][com.docker.diagnose.ipc][W] (b598f0f5-0) 658bf048-diagnose C<-S ConnectionClosed POST /idle/make-busy (776.792µs): Post "http://ipc/idle/make-busy": dial unix /Library/Containers/com.docker.docker/Data/backend.sock: connect: no such file or directory
[2025-01-08T16:18:19.170433000Z][com.docker.diagnose.ipc] (b598f0f5-3) 658bf048-diagnose C->S BackendAPI GET /idle
[2025-01-08T16:18:19.172700000Z][com.docker.diagnose.ipc][W] (b598f0f5-3) 658bf048-diagnose C<-S ConnectionClosed GET /idle (2.266542ms): Get "http://ipc/idle": dial unix /Library/Containers/com.docker.docker/Data/backend.sock: connect: no such file or directory
[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?
[FAIL] DD0017: can a VM be started? vm has not started: failed to open init.log: open /Users/majha/Library/Containers/com.docker.docker/Data/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?
[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? prereq failed: is the Docker engine running?
[PASS] DD0013: is the $PATH ok?
[FAIL] DD0003: is the Docker CLI working? prereq failed: is the Docker engine running?
[FAIL] DD0037: 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] 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 /Users/majha/Library/Containers/com.docker.docker/Data/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?
[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 5 warnings:
1 : The check: can a VM be started?
Produced the following warning: vm has not started: failed to open init.log: open /Users/majha/Library/Containers/com.docker.docker/Data/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: 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.
5 : 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 1 issue:
1 : The test: can a VM be started?
Failed with: vm has not started: failed to open init.log: open /Users/majha/Library/Containers/com.docker.docker/Data/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.
Reproduce
Expected behavior
Docker desktop application opens.
docker version
docker info
Diagnostics ID
Diagnostics ID: 05B327CD-06EE-4AD3-AADC-141210E40468/20250108162456
Additional Info
No response
The text was updated successfully, but these errors were encountered: