I am running Docker Desktop on an Ubuntu VM (24.04.4 LTS) through Proxmox (9.2.3). I was running v4.53 of Desktop and recently attempted to upgrade to 4.79. When I upgrade and restart, Docker Desktop starts in the background, but I cannot pull up the GUI. The Docker logo shows up in the top bar next to the network icon, but when I hit “Go to the Dashboard” nothing happens. I tried the AppArmor restriction fix, but it did not make a difference. Are there any other fixes I can try? Any logs that I can post to help diagnose?
For additional troubleshooting, I disabled hardware acceleration in the json file, upgraded to Ubuntu 25, and did a complete uninstall/clean/reinstall. Even with a fresh install, the GUI does not open but the underlying service does. What else am I missing?
You can try docker desktop stop and docker desktop start from the terminal. Or check the logs
docker desktop logs
For a better guide you can check the troubleshooting guide
https://docs.docker.com/desktop/troubleshoot-and-support/troubleshoot/
and report the issue on GitHub as described in the guide. It shows ho you can share your diagnostics ID that you can share with Docker on GitHub. They will have access to your shared logs.
I’m curious, do docker commands work while the GUI doesn’t, or nothing works?
Just posted a Github request for additional support. To answer your question, everything seems to start in the backend (so containers start and can be accessed through the website I setup), but I cannot perform any functions like pulling up the dashboard/change settings/check for updates.
This has been a known issue for quite some time and has impacted multiple people. When is someone going to fix this? @rimelek - what is the best way to get the devs looking at it?
The way I recommended in my previous post. The troubleshooting guide is not just a guide to troubleshoot but to find the GitHub repo where you can report your issue while sharing the logs privately. There were some improvements recently, but since I experienced none of the recent similar issues, so these are not issues affecting everyone. That means the recent fixes might not affect everyone either.
I saw that Docker tried making error messages more obvious (which I also recommended personally), but if you still have the problem discussed in this tpic, the best if you also report it on GitHub following the linked troubleshooting guide. The developers will see that and they can also analyse your logs whihc can reveal some new kind of causes and they can fix that or improve the error messages.