docker
Docker Engine Stopped
I tried to install Docker Desktop on Debian 12 following the instructions on Docker's official website. When I launched Docker Compose to install Apache Airflow using its docker-compose.yml, the installation was successful. However, after removing the containers using docker system prune --all -y and running docker compose down, I encountered an issue.
The next time I opened Docker Desktop, it seemed that the Docker Engine had crashed. I was unable to see Docker Desktop containers and images; instead, I only saw a spinning circle as it attempted to start the Docker Engine. After a while, I received an error indicating that the Docker Engine had stopped.
Reproduce
docker compose up airflow-init
docker system prune --all -y
docker compose down
close desktop-linux and then open termial and then type in terminal:
docker compose up airflow-init
Expected behavior Initializing the download and running the container for the second time after removing the previous containers.
Docker version:
Client: Docker Engine - Community
Version: 28.0.0
API version: 1.48
Go version: go1.23.6
Git commit: f9ced58
Built: Wed Feb 19 22:10:43 2025
OS/Arch: linux/amd64
Context: desktop-linux
docker info
Client: Docker Engine - Community
Version: 28.0.0
Context: default
Debug Mode: false
Plugins:
ai: Ask Gordon - Docker Agent (Docker Inc.)
Version: v0.7.3
Path: /usr/lib/docker/cli-plugins/docker-ai
buildx: Docker Buildx (Docker Inc.)
Version: v0.20.1-desktop.2
Path: /usr/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.32.4-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.38
Path: /usr/lib/docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Beta) (Docker Inc.)
Version: v0.1.4
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.4.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.16.1
Path: /usr/lib/docker/cli-plugins/docker-scout
Server:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 1
Server Version: 28.0.0
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
runc version: v1.2.4-0-g6c52b3f
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.1.0-31-amd64
Operating System: Debian GNU/Linux 12 (bookworm)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 19.1GiB
Name: sigma
ID: 1b32b508-d449-4f51-b250-4776c2fbec24
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
::1/128
127.0.0.0/8
Live Restore Enabled: false
I have the same on desktop (Ubuntu 24.10), it works on my main machine running 24.04, so I assume it is linked to this.
Although Ubuntu is based on Debian, it has its own package management system and repositories. I installed Docker Desktop on Debian 12.8 x64. The first time I ran Airflow, everything worked fine. However, after uninstalling and reinstalling it, I noticed that Docker Desktop was trying to start its Docker engine but failed. I reinstalled Docker Desktop two or three times, but the issue remained unresolved.
I am having a similar issue after upgrading my Docker Desktop from version 4.37 to 4.38 on a Debian 12 box.
I downgraded to my previous version and it's working fine.
The same is here since 4.38 version of DD. My system:
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
Linux serenity 6.11.10+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.11.10-1~bpo12+1 (2024-12-19) x86_64 GNU/Linux
If I remove the ~/.docker directory it starts and I may change the preferences in the gui.
After turning off and starting the gui after the first setup I can see only this:
The circle rolls some noticing amount of time and nothing. The docker engine is off. Only downgrade to the 4.37 version helps. Nevertheless even that version become unstable when building images with docker compose. Since 4.37 I see only regression in DD.
I have the same issue with Docker Desktop (4.39.0) on Debian 12. It works only right after initial setup and installation. Second run ends up with the "Starting the Docker Engine...".
Partial workaround for me is to remove .docker/desktop. Then it starts but it removes docker data as well.
Same here, Docker Desktop (4.39.0) on Debian 12. Initial setup was successful. Removing .docker/desktop works as well.
I'm seeing the same on Kubuntu 24.10. Deleting the ~/.docker directory solved it once, but then quitting and restarting docker desktop is broken again.
I also have the same issue on Ubuntu 24.10 and any version of docker desktop above 4.37.1 (178610)
i am seeing this repeated over and over again in the console log ~/.docker/desktop/log/vm/console.log
[2025-04-02T01:25:04.025312455Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:04.025605632Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:04.125980428Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:04.126321729Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:04.227004467Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:04.227819365Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:04.329123011Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:04.329438125Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:04.430032565Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:04.430242458Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:04.531995373Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:04.532295905Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:04.633182800Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:04.633557380Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:04.734234949Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:04.734442714Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:04.835335868Z][2minit.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:04.835625276Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:04.936132512Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:04.936449021Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:05.037279926Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:05.037464007Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:05.138107488Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:05.138419945Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:05.239023085Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:05.239808970Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:05.341240832Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:05.341685187Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:05.350979773Z][init.eth0 m] DHCPv4
[2025-04-02T01:25:05.442154169Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:05.442597535Z][init.socketforward ][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
[2025-04-02T01:25:05.543229214Z][init.socketforward ] connecting to TCP tcp+connect://192.168.65.1:1999
[2025-04-02T01:25:05.543418181Z][init.socketforward m][W] cannot set up multiplexer, will retry in 100ms: dial tcp 192.168.65.1:1999: connect: network is unreachable
Version 4.40.0 - still the same, Debian 12
Thank you for your report! However, using a sentence like this, similar to version 4.40, may not be helpful for developers. I would appreciate it if you could include error logs, system logs, and follow Docker guidelines for reporting errors. This would make it easier for developers to understand the issue. Thanks again!