So I open Docker Desktop and it want’s me to login. Okay. So I go through the process, it authenticates, ask to go to the app, and I’m still not logged in. So I install the update, go through thee login process again, and I’m still not logged in. So then I figured I’d try logging in via CLI. After deleting a bunch of unused tokens, I generated a new one on the web site and attempted to login via CLI. Here is the result:
“2025/07/04 11:08:05 notifying Desktop of credentials store update: getting credential helper update: error getting credentials - err: exit status 1, out: ‘exit status 2: gpg: public key decryption failed: No such file or directory
gpg: decryption failed: No such file or directory’
Login Succeeded”
Yet as you can see from this screenshot I’m not logged in:
For some reason, I always have to look fo the related documentation hard, but I think it used to be linked after the main installation guide on Linux. Now I couldn’t find it there, but there is a separate “Sign in” page
The “Login succeeded” message is strange. That part seems to be a bug. You could report it on GitHub if you want to help the developers
The error message part probably refers to the missing gpg key which you can generate as described in the documentation.
People are usually kind here, escpecially when a question is well writte like yours
Update:
By the way, signing n is not required in Docker Desktop unless you are using a feature that requires it. Sometimes Docker Desktop reports you need to sign in, when some tokens were expired and then logging out or in helps. Since you have the GPG error, I don’t think it is the case, but I still don’t understand why Docker Desktop wanted you to log in.
@rimelek thank you for your response and kindness. Having looked at the link you provided I do remeber going through that process once before. So I ran through the proceedure again and then got stuck as it kept refering me back to the original key which I fogot the password to. I finally found the .key files, deleted them, started Docker Desktop again, and I was signed in. So now I’m not sure what the problem is/was.
I suppose I could try creating the key again but as I’m logged into Docker Desktop now, is there even a point?
If you are logged in and you can log out and even log in to other registries, it should be fine. As long as you have no problem, you can continue using Docker Desktop.
I finally found the .key files, deleted them, started Docker Desktop again, and I was signed in. So now I’m not sure what the problem is/was. 