docker
cannot start docker desktop
running engine: waiting for the Docker API: engine linux/qemu failed to run: running VM: qemu: process terminated unexpectedly: exit status 1
Description
/opt/docker-desktop/bin/com.docker.diagnose check Starting diagnostics
[2024-11-14T12:24:13.311156803Z][com.docker.diagnose.ipc] 1431c421-diagnose -> <HOME>/.docker/desktop/backend.sock BackendAPI [2024-11-14T12:24:13.311350119Z][com.docker.diagnose.ipc] (c11048e3) 1431c421-diagnose C->S BackendAPI POST /idle/make-busy [2024-11-14T12:24:13.312126465Z][com.docker.diagnose.ipc] (c11048e3) 1431c421-diagnose C<-S 39165e4a-BackendAPI POST /idle/make-busy (753.94µs): 0xc00074c510 [2024-11-14T12:24:14.312567591Z][com.docker.diagnose.ipc] (c11048e3-1) 1431c421-diagnose C->S BackendAPI GET /idle [2024-11-14T12:24:14.314992841Z][com.docker.diagnose.ipc] (c11048e3-1) 1431c421-diagnose C<-S 39165e4a-BackendAPI GET /idle (2.318487ms): {"apisInFlight":{"heartbeat from Docker-Backend":1},"busyReason":["1 calls to heartbeat from Docker-Backend","timed activities: map[/idle/make-busy:28998055488 dial//run/guest-services/volume-contents.sock:36447393951]"],"timedActivities":{"/idle/make-busy":28998055488,"dial//run/guest-services/volume-contents.sock":36447393951},"vmRunning":true} [PASS] DD0038: are KVM user permissions configured? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [FAIL] DD0017: can a VM be started? vm has not started: vm has not started [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? [PASS] DD0034: is Context set to a Docker Desktop context? [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] 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] DD0036: is the credentials store configured correctly? [PASS] DD0033: does the host have Internet access? [PASS] DD0038: are KVM user permissions configured? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [WARN] DD0017: can a VM be started? vm has not started: vm has not started [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: vm has not started
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: vm has not started
The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.
Reproduce
every time I start docker desktop
Expected behavior
No response
docker version
Client: Docker Engine - Community
Version: 27.3.1
API version: 1.47
Go version: go1.22.7
Git commit: ce12230
Built: Fri Sep 20 11:41:00 2024
OS/Arch: linux/amd64
Context: default
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
docker info
Client: Docker Engine - Community
Version: 27.3.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.17.1-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.29.7-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.37
Path: /usr/lib/docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Alpha) (Docker Inc.)
Version: v0.0.15
Path: /usr/lib/docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /usr/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.27
Path: /usr/lib/docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: /usr/lib/docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.3.0
Path: /usr/lib/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: /usr/lib/docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.14.0
Path: /usr/lib/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
Diagnostics ID
25F96CC2-5808-4015-9A73-ADE2783FD881/20241114121909
Additional Info
No response
when u freshly installed docker desktop did your docker desktop run successfully or this is issue came after running your client many times correctly then this error occurred?
It's highly possible that something had went wrong during installation of docker
I installed it without an error. How should I overcome it ? Do I need to reinstall ubuntu host OS to fix it?
Just reinstall docker desktop follow the guide on dockers official website for installation
I had the same error on linux mint 21 after following the official docker desktop documentation. running engine: waiting for the Docker API: engine linux/qemu failed to run: running VM: qemu: process terminated unexpectedly: exit status 1
Afterwards, I rebooted and was able to start docker desktop. It turns out I can't run Oracle VirutalBox and Docker Desktop at the same time. I can reproduce the error by first starting virualbox and then starting docker desktop. Hope this helps.
