Closed chelseybeck closed 8 months ago
After more thinking, I believe this is probably not the fix, so I'm going to close this PR.
Why?
It looks like Chelsey's config is changed back to the old credsStore
key and I assume her docker is still working.
I asked @chelseybeck what's in her config.json and it's this:
{
"auths": {},
"credsStore": "desktop",
"currentContext": "default"
}
Where the auths list is empty. It would not be a good idea to post the contents if there were values in there, since it contains essentially plain-text passwords to the docker account.
This error is what happens when there's a connection interruption to the docker image registry when it's trying to download the image. I suspect this might be the actual cause, but it would be temporary and any action could be interpreted as having fixed the problem.
ERROR [web internal] load metadata for docker.io
Changing the key from credsStore
to credStore
can be dangerous because it can disable the configuration and cause docker to store plaintext passwords in auths
rather than in a secure credentials store. But what's likely to happen is docker detects there's no credsStore value set and prompts the user to set it. This is likely why @chelseybeck's config.json key got rewritten to the correct one after she changed it. Anyway, the plaintext behavior is demonstrated in the 3rd link I posted in a comment above.
I ran into this error setting up my local environment: ERROR [web internal] load metadata for docker.io/library/python:3.10-bullseye
I am adding a note for future users.