New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NoResponse POST /registry/credstore-updated #213
Comments
@oliversalzburg Did you find out the root cause here? |
@if-igor Funny you ask that, because I just ran into this again yesterday. I have no idea what causes this or what the fix is. I feel like this is temporary in nature. However, yesterday I had to resort to deleting Sorry to not have more details, but the Docker people don't seem to care either. |
What’s your operating system? Is this with Docker Desktop? Which version? |
@mat007 Windows 10 WSL Ubuntu 20.04 + Docker Desktop 4.3.2 (72729), also experienced on Windows 11 WSL Ubuntu 20.04 with same Docker Desktop. Also experienced with earlier versions. Can you tell me what this failure indicates? Maybe I can work around it more cleanly in the future. |
I guess the most likely cause would be that Docker Desktop isn’t started, is that plausible? |
It was definitely running. I'll set up the VM again where I last experienced this. If it reproduces again, I can submit diagnostics or otherwise troubleshoot. |
Set up the VM fresh and reproduced this right away. Diagnostics ID F0B9FFDF-7550-4863-BAE9-EFD51F7A8318/20220117183043 |
I can’t spot anything obviously wrong in the diagnostics. Basically that error means the Docker CLI can’t talk to the Docker Desktop application (sending an IPC to a named pipe). |
On Windows 10 21H1, Docker Desktop 4.4.3 (73365), WSL2 Ubuntu 20.04, I am having the same issue when running:
After entering the credentials I get the following error 3 times:
This is a new issue, it was not happening with previous versions of Docker Desktop. As workaround, downgrading to Docker Desktop 4.3.2 made the error not displayed anymore. |
@mat007 I understand the time mismatch is making this less helpful. My original report was for a case I experienced on my main workstation. I had no idea what to do with it, as the same process worked perfectly previously and it was unclear to me what could be the cause. Docker was definitely running. Since then, I only occasionally ran into this, every time without any detectable pattern to what the root cause is. Recently I was working on documentation and continuously used the "Windows 11 dev environment" Hyper-V template to create an environment to work in. This environment reliably produces the same error output. I'm also seeing this in Ubuntu 20.04 WSL inside that VM. (Before it is mentioned, I am aware of this being an unsupported environment. I do have nested virtualization extensions enabled and I also don't see why this would impact the credential helper.) In general, I think it'd be nice if this error could be caught and a better output could be generated. |
@lackovic does it work if you |
Ah so this is from WSL 2, right? |
This is WSL2, yes. If I |
It does work, but I already downgraded to Docker Desktop 4.3.2. I have not tried with the latest version.
WSL2 is the default WSL version nowadays. |
Same error here. WSL2 running Arch. Tried downgrading docker to
|
I'm having the same issue here, happened after I updated Docker to 4.4.3 too |
I am having the same issue with Docker 4.4.3. |
Changing from |
Thanks @walkafwalka -- that fixed it for me. I updated credStore in |
We have found and fixed the issue, and will be releasing a new Docker Desktop version shortly. Changing the credential manager in |
I feel like I probably originally had a different issue than what's being discussed as the root cause now, but I'm glad the solution is still to just not use the credential helper. The UX in this case sucks hard, but I have no hope that is going to change. Thus, closed. |
|
I also had the same issue with Docker Desktop 4.4.3 and WSL 2. After updating to 4.4.4 the problem was resolved. Thank you @mat007 for the quick fix. |
Trying to
docker login
results in the following output:The text was updated successfully, but these errors were encountered: