-
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
Error on pushing image to GCR #1791
Comments
Also getting this error |
Having this issue also!!! |
Using Workload Identity to push images to GCR is producing the same error as OP posted. |
Seeing this error as well. |
Dupe of #1786 |
I posed on the dupe but I'm wondering if its somehow here cf4822c |
Same, downgraded to 1.6.0 - fixed issue for me =( |
We are facing this issue as well |
Same here. Using v1.6.0 instead of latest solved the problem for me |
Same issue for us this morning. Rolling back to 1.6.0 solved it for now. |
Same issue here :/ Workaround worked thanks |
Same here, looks like this could be a regression of #1242. |
…ushing images to gcr
Thanks fix is the way! #1794 |
Having this issue too. Had to tie down the version v1.6.0 |
is this live yet? |
Sam error happend to me as well, but downgrading to v.1.6.0 did not solve the error :/ |
Same issue here. $ mkdir -p /kaniko/.docker
$ echo "{\"auths\":{\"gcr.io\":{\"auth\":\"$(echo -n _json_key:$(cat service-account-key.json) | base64 | tr -d "\n")\"}}}" > /kaniko/.docker/config.json |
Same issue here, using Kaniko for test environments, all build pipelines were broken. Temporarily fixed with rollback to version 1.6.0. |
Same issue with image builds on gitlab runner in GKE using workload identity auth. |
I am using gcloud to build dockers. gcloud config set builds/use_kaniko True Is there a workaround or way to downgrade to 1.6.0? |
@corveen and anyone who's struggling with this regression that's been introduced and left unsolved 3 days ago (yes, unbelievable) along with another regression in gcloud CLI preventing AppEngine deploys that has been introduced on the same day in SDK 361.0.0 and has not been addressed to this day either, here's what we did:
This is the equivalent of using Relevant documentation that helped us solve this issue: |
This reverts commit 45c2dd5. I believe the latest is now pointing back to 1.6 until the proper fix is landed. GoogleContainerTools/kaniko#1791 GoogleContainerTools/kaniko#1794
Keeping version 1.6 is now the answer? Why no one revert this 1.7 version? |
The current |
Current latest works for me. I think it was fixed.
… On 21 Dec 2021, at 20:48, Jason Hall ***@***.***> wrote:
Keeping version 1.6 is now the answer? Why no one revert this 1.7 version?
The current :latest used by gcloud points to 1.6.0, since there was a bug in 1.7.0.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.
|
I was able to use 1.7.0 by mounting a docker config using the SA creds https://issueexplorer.com/issue/GoogleContainerTools/kaniko/1791#10012106
@Keramblock latest got reverted to 1.6.0 due to issues |
Also tested v1.8.0 and v1.8.1, same issue. Reverted back to v1.6.0, now it works :/ |
Still an issue when using 1.9.1. Used @nicolas-goudry's suggestion which works.
|
Can anyone here comment on if this issue is still occuring for them w/ the latest version of Kaniko |
I can't reproduce this issue anymore. We are using v1.9.2 (and testing v1.12), no issue so far. In our case, this was a configuration issue. We are using GCR auth via workload identity. Till v1.6 we had to provide a Docker config file (
Since at least v1.8 (maybe even v1.7) you don't need, actually you cannot have this Docker config file anymore. If this file is present, Kaniko v1.8 or newer fails with an auth error as reported in this issue. And vice versa, v1.6 does not work without the config file above. If you are using the newest version of Kaniko with GCR and workload identities, omit the Docker config file. Keeping an empty one |
Thanks @hudac, closing this issue as I believe this is resolved @ HEAD |
Actual behavior
Getting an error on kaniko with GCR after latest update (version 28a6bdc-debug
1.7.0-debug)
Expected behavior
image a0c96b4-debug is OK (ver 1.6.0-debug)
To Reproduce$REGISTRY_ACCESSKEY > $ {CI_PROJECT_DIR}/gcr.json$CI_PROJECT_DIR --dockerfile ./Dockerfile --destination $ {IMAGE}
printf
/kaniko/executor --context
Additional Information
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 "eu.gcr.io/******/****************:": creating push check transport for eu.gcr.io failed: GET https://eu.gcr.io/v2/token?scope=repository%3A***********%2F*****%3Apush%2Cpull&service=eu.gcr.io: UNAUTHORIZED: Not Authorized.
1.7.0-debug
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: