-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Push access is denied, even though push access is 100% available #1697
Comments
Please test with #1636 |
I did: docker buildx use "$(docker buildx create --driver-opt image=moby/buildkit:master)" Then I ran the build script again, with the This was the result:
|
The last one might've been an unpleasant fluke or there have been further updates to |
This is currently an issue on GCP Cloud Build pushing to GCP Artifact Registry when the build is longer than an hour. I filed docker/buildx#1205 with the details. There is a workaround (build without --push, stop builder, build again). Full details with reproducible example can be found at dougdonohoe/build-timeout. |
Given this Docker project:
https://github.com/theAkito/kubedigger/tree/f7bdf68171d069fd834185dbe2e1521456ac998d
Building the images resulted in the following behaviour:
How is it possible to get
401 Unauthorized
on an empty repository, while pushing the exact same images, except with different tags (0.5.0
->latest
) again and it works?If you look at the build script and see the
buildx
commands at the bottom, you see that it just uses the cached images and uploads them, basically repeating the same operation that failed before, but now resulting positively.Not sure if these issues are related:
moby/moby#39019
#1142
#1271
The text was updated successfully, but these errors were encountered: