Skip to content
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 checking push permissions -- make sure you entered the correct tag name #2222

Open
eravindar12 opened this issue Aug 24, 2022 · 9 comments
Labels
area/authentication area/registry For all bugs having to do with pushing/pulling into registries issue/push-permissions kind/bug Something isn't working priority/p0 Highest priority. Break user flow. We are actively looking at delivering it. priority/p1 Basic need feature compatibility with docker build. we should be working on this next. registry/gcr regression/v1.6.0 regression

Comments

@eravindar12
Copy link

I see below the issue and how to fix it.

$ export DOCKER_REPOSITORY=${DOCKER_REPOSITORY:-ecommerce/$CI_PROJECT_NAME${APP:+/}$APP}
$ echo "{\"auths\":{\"$DOCKER_REGISTRY\":{\"username\":\"$DFWP_HARBOR_USER\",\"password\":\"$DFWP_HARBOR_PASS\"}}}" > /kaniko/.docker/config.json
$ /kaniko/executor \ # collapsed multi-line command
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 "dfwpharb01.sial.com/ecommerce/aem-cms/aem-dispatcher:release-integration-3513e70d": POST https://dfwpharb01.sial.com/v2/ecommerce/aem-cms/aem-dispatcher/blobs/uploads/: UNAUTHORIZED: unauthorized to access repository: ecommerce/aem-cms/aem-dispatcher, action: push: unauthorized to access repository: ecommerce/aem-cms/aem-dispatcher, action: push

@iJebus
Copy link

iJebus commented Aug 29, 2022

I'm seeing similar with pushing to GCP artifact registry, looks like possible regression of #1786? Per the comments on that issue, pushing works when using 1.6.0.

@vmamidala-conga
Copy link

ECR Push operation is failing with following error using kaniko, it used to work until yesterday.
Kaniko version - v1.6.0
I tried testing it out with v1.7.0, v1.9.0 (latest) but still facing same issue. Any one had same issue? and resolved? I really appreciate you help
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 "https://ecr-private-repo/uploads": Post "https://ecr-private-repo/uploads": EOF

@mofirouz
Copy link

mofirouz commented Nov 4, 2022

Yep same issue here - works with v1.6.0, but any newer and it's borked.

@aaron-prindle aaron-prindle added registry/gcr issue/push-permissions area/authentication area/registry For all bugs having to do with pushing/pulling into registries regression regression/v1.6.0 priority/p1 Basic need feature compatibility with docker build. we should be working on this next. priority/p0 Highest priority. Break user flow. We are actively looking at delivering it. kind/bug Something isn't working labels Jun 25, 2023
@jessequinn
Copy link

v1.6.0 does not work for me .. all the way up to 1.12.1. It was working yesterday.

@zijiwork
Copy link

zijiwork commented Aug 3, 2023

Depending on this issue is not resolved, tekton kaniko version upgrade from 1.5.1 to 1.13.0 will not work

@tirelibirefe
Copy link

ECR Push operation is failing with following error using kaniko, it used to work until yesterday. Kaniko version - v1.6.0 I tried testing it out with v1.7.0, v1.9.0 (latest) but still facing same issue. Any one had same issue? and resolved? I really appreciate you help 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 "https://ecr-private-repo/uploads": Post "https://ecr-private-repo/uploads": EOF

Hello @vmamidala-conga
Were you able to fix the problem? I have the same problem; I tried v.1.16.0 and 1.17.0, nothing changed.

Thanks & Regards

@tirelibirefe
Copy link

1.5.1

1.12.1 didn't work at me.

@ALGHARRASS-AYOUB
Copy link

ALGHARRASS-AYOUB commented May 17, 2024

you must verify the encoded value of auth. if you use "username:password" to authenticate you must encode it as :
echo -n "username:password" | base64
and not : echo username:password | base64.

then you can put the content below to this location /kaniko/.docker/config.json
the content of the file:

{
       "auths": {
                "YOUR_CI_REGISTRY": {
                 "auth": ENCODED_BASE64_STRING"
                }
}

@tbernacchi
Copy link

same here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/authentication area/registry For all bugs having to do with pushing/pulling into registries issue/push-permissions kind/bug Something isn't working priority/p0 Highest priority. Break user flow. We are actively looking at delivering it. priority/p1 Basic need feature compatibility with docker build. we should be working on this next. registry/gcr regression/v1.6.0 regression
Projects
None yet
Development

No branches or pull requests

10 participants