Docker Desktop not starting
cberk17 opened this issue · 1 comments
Description
The docker engine hangs when I try to run it. I ran the diagnostic through the troubleshooting section and get the following: running engine: waiting for the Docker API: context deadline exceeded
Reproduce
I am trying to open the engine through the applications
Expected behavior
The engine should start
docker version
Client:
Version: 27.1.1
API version: 1.46
Go version: go1.21.12
Git commit: 6312585
Built: Tue Jul 23 19:54:12 2024
OS/Arch: darwin/arm64
Context: desktop-linux
docker info
Client:
Version: 27.1.1
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.16.1-desktop.1
Path: /Users/cberk/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.29.1-desktop.1
Path: /Users/cberk/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.34
Path: /Users/cberk/.docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Alpha) (Docker Inc.)
Version: v0.0.14
Path: /Users/cberk/.docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /Users/cberk/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.25
Path: /Users/cberk/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: /Users/cberk/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.3.0
Path: /Users/cberk/.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/cberk/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.11.0
Path: /Users/cberk/.docker/cli-plugins/docker-scout
Server:
ERROR: Cannot connect to the Docker daemon at unix:///Users/cberk/.docker/run/docker.sock. Is the docker daemon running?
(I cannot get the engine to start)
Diagnostics ID
3E6A1E41-670C-4572-90F0-C42584094BE2/20241118160425
Additional Info
No response
Hi @cberk17 ,
according to the logs, it seems the VM is running out of space: Unable to get the TempDir under /var/lib/docker: mkdir /var/lib/docker/tmp: no space left on device
.
It could be related to switching to containerd
: the image store of containerd
is a new one but the previous store is not deleted.
Can you try to disable containerd
(doc), then delete all your images, then re-enable containerd
?
It should free up disk space and let your work without issues.