Failed to authorize: rpc error: code = Unknown desc = failed to fetch oauth token: unexpected status: 401 Unauthorized

Same problem. Automated Builds do not work since morning.

1 Like

My organization got the same problem too.

We are having the same issue.

Yes but some reasons why somebody needs to go in workarounds when everything was configured and worked perfect until today :frowning:

1 Like

@DockerSupport can you help us?

1 Like

Same issue here:

#3 ERROR: failed to authorize: rpc error: code = Unknown desc = failed to fetch oauth token: unexpected status: 401 Unauthorized
------
> resolve image config for docker.io/docker/dockerfile:1:
------
error: failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: failed to authorize: rpc error: code = Unknown desc = failed to fetch oauth token: unexpected status: 401 Unauthorized
Build failed using Buildkit

Same issue here, has anyone heard anything from @DockerSupport?

actually I don’t receive a reply from the support

1 Like

Same here. Did anybody make any progress?

Our organization is experiencing the same problem with all our builds.
@DockerSupport?

#4 [auth] library/node:pull token for registry-1.docker.io
#4 sha256:19706794fc14b42b1eeca8e1198ff703e6409e72d0ee76472b846b0fd8262f34
#4 DONE 0.0s
#3 [internal] load metadata for docker.io/library/node:12-stretch
#3 sha256:78f0a37b8d0eca7cada27ca44593d68a20b893198c88d1ef3acfb560578c1d8f
#3 ERROR: failed to authorize: rpc error: code = Unknown desc = failed to fetch oauth token: unexpected status: 401 Unauthorized
2 Likes

Thanks the community for sharing information. I found out earlier it is working now and want to share this good news to all of you!

4 Likes

I don’t know why but this support looks like not responding usually :frowning:

1 Like

Same problem here with my organitzation

Just started a new build. Problem seems solved for us atm…

1 Like

@amcorreia That’s been my experience as well. I reached out to them with something time-sensitive related to billing and after a few months of silence I had to resolve it through my bank. They seem to be understaffed.

1 Like

Same here. Did anybody make any progress?

First login to docker using docker cli command (docker login) then try to build the image

This might sound crazy but I tried again a few hours later and the problem resolved itself… Prior to that, I’d logged out of Docker with the CLI, and then logged back in with my Docker Hub username and password (e.g. docker logout && docker login -u <username> -p <password>). No idea why it worked, but re-logging in, and then waiting a few hours, fixed it… Logging out and logging in did NOT initially work, but a few hours later the problem magically resolved itself… Wish I could be more helpful than that

2 Likes

I got this working by disabling buildkit. My issue was being behind a firewall, and disabling buildkit made everything good.
image

3 Likes

Awesome , Even in my case the issue was being behind the firewall .
Disabling the buildkit worked