-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 Permission Error on latest #1786
Comments
Same here. My environment is:
I've confirmed when I specify |
My environment is also:
If I specify gcr.io/kaniko-project/executor:edge, it also works. |
+1
|
Same here. My environment is: Google Cloud Build I've confirmed when I specify gcr.io/kaniko-project/executor:v1.6.0, it works expectedly. |
Same My environment also is:
|
This is also broken, cannot push the images to GCR |
Same here:
Downgrading to 1.6 works |
Same here. My environment is:
This workaround works for me:
|
Getting the same issue. My environment is:
Changing the container reference in my |
Could this fix be the cause? |
In reference to the comment by @jonbuffington
Keep in mind that this image is from May 7, 2020. I think it's better to use the |
Same issue, Google Cloud Build & Google Container Registry here |
RIght. Thanks! |
Diffing v1.6.0 and v1.7.0 i noticed a change to conditionally loading a credential helper here v1.6.0...v1.7.0#diff-4c345264209a6b2e4584f42b5fc96ef58595aef6dbb3b342e02aa723ce7323d7R68-R81 I know zero about this codebase so probably not reading the code right but seems maybe related |
The latest version of kaniko (https://cloud.google.com/build/docs/kaniko-cache) is failing to build lit.dev with a permissions error. Many other users are seeing the same thing today. Downgrading temporarily works. See GoogleContainerTools/kaniko#1786
Same:
|
Same problem. Pinning 1.6.0 ( |
Same problem here. Exactly when i started learning CI/CD with kaniko so naturally i assumed that the error was on my part. Anyone has any alternative to using gcr.io/kaniko-project/executor:debug with GCP? Im very new to that. EDIT: For anyone using debug version use for now "gcr.io/kaniko-project/executor:v1.6.0-debug" instead of "gcr.io/kaniko-project/executor:debug". At leat that did the trick for me. |
myself also tried unable to push image to gcr error checking push permissions -- make sure you entered the correct tag name, and that you are authenticated correctly, and try again: checking push permission for "gcr.io/[MASKED]/[MASKED]:2.0.10": creating push check transport for gcr.io failed: GET https://gcr.io/v2/token?scope=repository%3A[MASKED]%2Flb4b-mi%2F[MASKED]%3Apush%2Cpull&service=gcr.io: UNAUTHORIZED: Not Authorized. |
I managed to fix it by explicitly calling the
Where registry-path is the root path for the GCP Container Registry like |
I did some digging in #702 (comment) (which probably should have been in this issue 🤦♂️), but it sounds like the |
Same error using Gitlab CI with gitlab runner (docker executor)
and
I also tryed regenerating the service acount key (the json file), giving our service account Editor role just in case but it didn't help |
Yea this is not about permissions, unfortunately - it's just that Kaniko no longer generates the authentication token from env credentials, so it's a 401 error not 403.. |
+1 Same as everyone else My environment is: Google Cloud Build Downgrading to 1.6.0 fixes the error, but this is not a viable work around. Updating hundreds of projects to use 1.6.0 is hardly a solution. Why was this change made without proper QA testing to make sure it doesn't break anything? |
+1, although I'm using Google Artifact Registry as my target from Cloud Build, not Container Registry. |
We’ve rolled back the Kaniko images to point to v1.6.0. |
@briandealwis thanks! Btw are there any regression/integration tests that could prevent this kind of issue from cropping up again? It would be really helpful to test Kaniko in all of the supported environments, if you have time to implement that :-) |
Permission error in 1.7.0 GoogleContainerTools/kaniko#1786
This reverts commit 0a4b18d. Kaniko 1.7.0 version is unable to push latest tag on gcr: GoogleContainerTools/kaniko#1786 (comment)
The latest version now works for me for a few days. Closing this. |
It does not work, was this resolved. ! have same issue, tried every build of kaniko |
Same issue here, we are using the |
Actual behavior
Permission error on pushing to google container registry.
Expected behavior
It should successfully push, I reverted to 1.6.0 and it works great.
To Reproduce
Make a google build with this yaml:
Additional Information
Any dockerfile will reproduce the error.
gcr.io/kaniko-project/executor:latest
digest: 8504bde9a9a8c9c4e9a4fe659703d265697a36ff13607b7669a4caa4407baa52
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: