-
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 checking push permissions 0.17.0 onwards #1179
Comments
+1 experiencing similar issue using artifactory-jcr https://github.com/jfrog/charts/tree/master/stable/artifactory-jcr |
Sorry for jumping late. |
Tried with the latest
There are no other lines. Note that this still works with 0.16.0 and below. My best guess is something changed in how go-containerregistry performs auth. Edit:
|
Update: Seems to have resolved itself. I'm running into this same error. My setup is GitLab & GitLab Runner in docker. The private registry is Nexus. Nexus is accessible and I'm able to request tokens outside of my build job. build-docker:
stage: build
tags:
- docker
image:
name: gcr.io/kaniko-project/executor:debug-v0.22.0
entrypoint: [""]
script:
- ls $CI_PROJECT_DIR
- ls $CI_PROJECT_DIR/target
- echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASS\"}}}" > /kaniko/.docker/config.json
- /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/docker/Dockerfile --destination $CI_REGISTRY/products/lc-service:$CI_COMMIT_TAG
only:
- tags GitLab Runner Output:
Trying to run with
|
same issue here, gitlab-runner + kaniko debug 0.16.0, private registry is harbor. |
same here gitlab and kaniko v0.23.0 |
Closing as this is fixed for me using 1.2.0. |
We use a private artifactory registry which works completely fine for all tags from 0.10.0 to 0.16.0, using gitlab with a command like:
From v0.17.0 to v0.19.0, this yields “error checking push permissions...unsupported status code 401”
I do not see anything in the change log that seems relevant to this but did see the note under 0.18.0 that v0.17.0 introduced many regressions.
The text was updated successfully, but these errors were encountered: