I have a fresh installation of Fedora 43. I have only installed Nvidia drivers and now docker.
I have followed these instructions to get Docker / Docker Desktop installed: Fedora | Docker Docs
Everything appears to be installed and working, I can start / stop / restart docker desktop from the CLI, but I cannot get the Docker Desktop GUI to lauch at all after the initial time it opened. This has persisted after a reboot.
I get this information from my terminal:
bcmcpher@fedora:~$ docker version
Client: Docker Engine - Community
Version: 29.3.0
API version: 1.53 (downgraded from 1.54)
Go version: go1.25.7
Git commit: 5927d80
Built: Thu Mar 5 14:29:24 2026
OS/Arch: linux/amd64
Context: desktop-linux
Server: Docker Desktop 4.63.0 (220185)
Engine:
Version: 29.2.1
API version: 1.53 (minimum version 1.44)
Go version: go1.25.6
Git commit: 6bc6209
Built: Mon Feb 2 17:17:24 2026
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v2.2.1
GitCommit: dea7da592f5d1d2b7755e3a161be07f43fad8f75
runc:
Version: 1.3.4
GitCommit: v1.3.4-0-gd6d73eb8
docker-init:
Version: 0.19.0
GitCommit: de40ad0
bcmcpher@fedora:~$ docker desktop version
Docker Desktop CLI plugin version: v0.3.0
bcmcpher@fedora:~$ docker compose version
Docker Compose version v5.0.2
I did not notice that. I’ve not worked with Fedora much (mostly Debian / Ubuntu). It didn’t occur to me that I was too recent. The last reference in the release notes of Fedora is 35 and there’s no mention of Gnome issues in the UI in the last year or so.
I don’t know if the reason of the issue is the Fedora version. We had multiple reports about the GUI not working in latest Docker Desktop versions. I think people claim it started after v4.59.1, so you could try installing that just to confirm if an older version works.
If not even an older version works, we can try to find out if Fedora 43 could be the reason or not.
But unless someone opens a ticket in the Desktop Feedback repository
The developers will likely not see these reports soon. We can sometimes let Docker know about issues, but since I cannot reproduce this and all the upgrades worked for me, I could not provide useful diagnostics. If you have time, it could help a lot if you could reinstall the new version and run diagnostics as described here
and share your diasgnostics ID with the developers on GitHub also as described in the troubleshooting guide. They can then check your logs. We have no access to those.