-
Notifications
You must be signed in to change notification settings - Fork 764
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
Pushing 2 tags to Quay gives unauthorized error #665
Comments
@sozercan that issue seems slightly unrelated I think because their issue is caused when they run Do we have a contingency plan? Such as using docker hub rather than quay if this issue persists? I can take a further look shortly - when is our next release scheduled? |
Upon reading through that issue again, it could be related based on the last comment 14 hours ago
We should test out a few options. Perhaps we should either use Either of these approaches would need someone with permission to push to quay to test and confirm what works best. |
FYI, I done the test in moby/buildkit#1440. Pushing 2 tags at once works, at least by directly calling buildctl.
|
@mbarbero did you also attempt to do it with the same approach as being done in the Makefile? |
added a workaround in #672. I am suspecting either local or quay cache issue as the first tag seems to be pushed fine, but when second tag is pushed it fails. |
@sozercan I left some feedback to the PR, I think there may have been a slight misunderstanding of the problem. |
gcr.io has an issue that it's not possible to update multi-arch images (see eclipse-che/che#16983 and open-policy-agent/gatekeeper#665). We're now relying on ghcr.io instead, which I verified doesn't have this bug, so we can stop skipping these pushes.
gcr.io has an issue that it's not possible to update multi-arch images (see eclipse-che/che#16983 and open-policy-agent/gatekeeper#665). We're now relying on ghcr.io instead, which I verified doesn't have this bug, so we can stop skipping these pushes.
What steps did you take and what happened:
When CI is pushing 2 tags to quay.io (for
<sha>
anddev
orlatest
and<version>
), Quay doesn't seem to support this behavior using buildx (this seems to work fine in Docker Hub).CI pushes the first tag successfully, and then gives
ERROR: failed commit on ref "manifest-sha256:cf45078539d967014f41593b81f702079247e8261cf48919d06d3391da55d66f": unexpected status: 401 UNAUTHORIZED
error when pushing 2nd tag.example: https://github.com/open-policy-agent/gatekeeper/runs/736616057?check_suite_focus=true
We should fix this before the next release, otherwise we can't push
latest
and<version>
tags with same hashes.relevant issue: moby/buildkit#1440
cc @xunholy
The text was updated successfully, but these errors were encountered: