kaniko: error checking push permissions when pushing to insecure registry
Actual behavior When pushing to an insecure registry, process fails with the message:
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 "adress:port/name:tag": Get https://server:port/v2/: http: server gave HTTP response to HTTPS client
Expected behavior Kaniko builds and pushes Image to registry. Still working at v0.9.0
To Reproduce Steps to reproduce the behavior:
config.yaml
...
args: ["--dockerfile=Dockerfile",
"--insecure-registry=YOUR_OWN_INSECURE_REGISTRY",
"--destination=AN_EXISTING_DESTINATION",
"--insecure"]
...
About this issue
- Original URL
- State: open
- Created 5 years ago
- Reactions: 9
- Comments: 27 (3 by maintainers)
Just a heads up that the latest kaniko version (v1.7.0 ) seems to be causing this problem for my team: https://github.com/GoogleContainerTools/kaniko/releases
Downgrading to v1.6.0 fixed the problem.
I have found the problem and need to set the variable of Gitlab as a non protected variable!!!
So how can we solve this problem in the end?
i have the same issue now on the pipeline that worked few days ago.
So??? How to fix this sh… ? There is no answer https://github.com/GoogleContainerTools/kaniko/issues/1179 to
Hey @CeadeS could you try again with
gcr.io/kaniko-project/executor: 51734fc3a33e04f113487853d118608ba6ff2b81? I’m wondering if #685 will fix your issue.