Repository navigation
Docker desktop is unable to start docker engine (Debian 12.10, Docker Desktop 4.40.0) #284
Description
Description
Hi, my Docker Desktop app is unable to start the Docker Engine. The message “Starting the Docker Engine” along with a loading indicator appears indefinitely.
I followed the installation guide from the official site and completed all the steps. The very first time, it worked well, but after quitting and reopening the app, it fails to start the Docker Engine.
A workaround for this issue is to remove the .docker/desktop directory. After doing so, the app prompts the license agreement again and starts with the engine running.
The workaround is only partial and will remove all the data so it is only to run the app.
OS Version: Linux Debian 12.10.0
App version: 4.40.0 (187762)
Reproduce
- Install docker as described in Debian | Docker Docs
- Install docker desktop as described in Debian | Docker Docs
- Run Docker Desktop
- Quit Docker Desktop
- Open Docker Desktop again
Expected behavior
Docker desktop should start the docker engine.
docker version
Client: Docker Engine - Community
Version: 28.0.4
API version: 1.48
Go version: go1.23.7
Git commit: b8034c0
Built: Tue Mar 25 15:07:22 2025
OS/Arch: linux/amd64
Context: desktop-linuxdocker info
Client: Docker Engine - Community
Version: 28.0.4
API version: 1.48
Go version: go1.23.7
Git commit: b8034c0
Built: Tue Mar 25 15:07:22 2025
OS/Arch: linux/amd64
Context: desktop-linux
Server: Docker Desktop 4.40.0 (187762)
Engine:
Version: 28.0.4
API version: 1.48 (minimum version 1.24)
Go version: go1.23.7
Git commit: 6430e49
Built: Tue Mar 25 15:07:22 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.26
GitCommit: 753481ec61c7c8955a23d6ff7bc8e4daed455734
runc:
Version: 1.2.5
GitCommit: v1.2.5-0-g59923ef
docker-init:
Version: 0.19.0
GitCommit: de40ad0Diagnostics ID
9D843CBF-DFE2-4B09-B91A-55B68897B2A9/20250409164319
Activity
pippo111 commentedon May 6, 2025
I've just tested v4.41.1 and looks like it works as expected.
CPioGH2002 commentedon Jun 7, 2025
Feel free to close the issue if it was solved with the update. :-)