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 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.9.0
App version: 4.39.0 (184744)
Actual Result: Docker Desktop runs, but the Docker Engine does not start and remains stuck on “Engine starting…”. Expected Result: Docker Desktop runs, and the Docker Engine starts successfully (“Engine started”).
It seams you found the workaround that other users could have recommended on the forum, although deleting that folder also deletes all data if I remember correctly, but I’m not on Linux now. If it is a bug in the upgrade process, you could let the developers know about it on GitHub
You are correct. The workaround is only partial and will remove all the data so it is only to run the app. Btw. how to edit my post? I would like to add that info to be aware of the outcome of the workaround.
Hi,
I got the same issue on Debian 12
Docker Desktop version 4.40.0
Your workaround is the only way I was able to get passed the docker engine not being able to start.
Thank you very much!
This really is not a workaround unfortunately. I am trying to host an ERPNext stack from my Debian 12 server. Literally every single time I quick docker desktop or have to power down my computer I come back and have to delete my images and other data by removing the specified folder? That is absolutely not a proper workaround. Has any development or progress been made on this yet? Is it safe to say Docker Desktop is 100% broken on Debian 12? Can anyone advise whether Ubuntu Server installs are having the same issue and so if it is Docker Desktop = Broken On Linux in general? I absolutely must get the stack up but having to lose data that should persist brings the usability to 0.
It is broken. As I mentioned the workaround is only partial. In theory you could dump and restore your data but that is not the way we want to develop anything.