-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Facing an issue while pushing the docker image to gcr. This was success few hours back #1793
Comments
have the same issue now... |
I am also facing the same issue. |
Dupe of #1791 tagging the kaniko build to v1.6.0 should fix it |
Yep, I'm using a sleep command in my Jenkins pipeline, so I re-tagged to:
|
Thank you very much! it worked with v1.6.0-debug. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
build-my-project-main-1634746396-3138521323: For verbose messaging see aws.Config.CredentialsChainVerboseErrors
build-my-project-main-1634746396-3138521323: error checking push permissions -- make sure you entered the correct tag name, and that you are authenti
cated correctly, and try again: checking push permission for "gcr.io/my-project/my-project/main:94839f3f599cee88e3c81919f3e98d3a78c17ced": creati
ng push check transport for gcr.io failed: GET https://gcr.io/v2/token?scope=repository%3Amy-project%2Fmain%2Fmain%3Apush%2Cpull&service=gc
r.io: UNAUTHORIZED: Not Authorized.
The text was updated successfully, but these errors were encountered: