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
unexpected status: 401 Unauthorized #327
Comments
So I tried it a couple more times again and now its working:
No idea what the issue can be... |
I'm experiencing this in my CI builds, after Here is a full build history if anyone is interested: EDIT: I should note that retriggering this build works as it uses the cached docker images and pushes faster. |
I ran into this problem today creating large images. What I did was use the --cache-to flag when building it, then when I go to push it to dockerhub I log in and use --cache-from.
As long as it uploads the image somewhat quickly, it hopefully shouldn't time you out. Note that this does take a lot more disk space. I made a VM and gave it 64gb of disk space, and with a 7gb docker image crosscompiled to x86 and arm it ran out of disk space while caching all of the layers. Hope that helps a bit. EDIT: You could also play around with caching to/from a registry. I mentioned local caching because my internet would be a bottleneck, but it might reduce disk usage if that is a concern, but I havent personally tested it. |
Please test with moby/buildkit#1636 |
congratulation! now I can push. each push is a success, when before it mostly failed (after running for 10 minutes). |
See docker/buildx#327 Signed-off-by: Andrey Smirnov <smirnov.andrey@gmail.com>
See docker/buildx#327 Signed-off-by: Andrey Smirnov <smirnov.andrey@gmail.com>
See docker/buildx#327 Signed-off-by: Andrey Smirnov <smirnov.andrey@gmail.com>
I'm hitting this at the moment with Quay.io. GitHub Container Registry works OK. I'm able to reproduce this locally via CLI. The interesting thing that a regular Another interesting thing that the first push to Quay.io (when images not yet existed) worked OK. |
@tyranron same deal here: pushing to Quay.io from a GitHub Actions workflow on the subsequent run. |
I think you guys are hitting containerd/containerd#4622 (comment) |
Exact same issue here with me. |
Same issue here! |
because we hit docker/buildx#327 (#patch)
Suggested fix when hitting the 401 authorized error that we are when trying to push new images: docker/buildx#327 Signed-off-by: David Bond <davidsbond93@gmail.com>
I think the fix for containerd/containerd#4622 (comment) found its way into containerd v1.5.0 via containerd/containerd#4854 It looks like moby/buildkit pulled in containerd v1.5.0 via moby/buildkit#2102 23 days ago I'm wondering when we might expect a release of buildx that include this fix. Do we need to wait for a release of buildkit, or would y'all be open to pulling in something sooner? |
Should be fixed since BuildKit 0.8.2. |
Suggested fix when hitting the 401 authorized error that we are when trying to push new images: docker/buildx#327 Signed-off-by: David Bond <davidsbond93@gmail.com>
Hi All,
So I saw this was posted before but without a proper solution or breakdown why this happens. #139 (comment)
I'm also having this issue from time to time and its really unclear what it triggers.
First I do the docker login and that goes well, after that I start the buildx for the 2 images but I still get the 401 error in the end as you can see. I'm using it on Mac Docker Desktop 2.3.2.0 Edge. if you need additional information please let me know.
The text was updated successfully, but these errors were encountered: