Kaniko: error checking push permissions when pushing to insecure registry

Created on 20 Jun 2019 · 9Comments · Source: GoogleContainerTools/kaniko

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"]
...

arebehavior kinbug prioritawaiting_evidence prioritp1

Source

CeadeS

👍7

All 9 comments

I hit with the same issue when using docker image by tag latest (updated 13 hours ago).
I noticed issue with hostname resolution.

vijaySamanuri on 20 Jun 2019

Look at
Duplicate of #683

cn-sunletian on 2 Jul 2019

Hey @CeadeS could you try again with gcr.io/kaniko-project/executor: 51734fc3a33e04f113487853d118608ba6ff2b81? I'm wondering if #685 will fix your issue.

priyawadhwa on 27 Sep 2019

👍1

@CeadeS and @CeadeS Can you please confirm?

tejal29 on 28 Sep 2019

This is now fixed. thank you for your patience.

tejal29 on 18 Mar 2020

@tejal29 , how did you fixed this issue, could you let us know

pvgbabu on 20 Jul 2020

So??? How to fix this sh... ? There is no answer https://github.com/GoogleContainerTools/kaniko/issues/1179 to

just4est on 17 Sep 2020

👎1

@just4est and @pvgbabu #685 should respect --insecure flag even if the --insecure-registries does not contain the destination image registry.

663 should skip tls verficaition for your insecure registry.

Can you try --insecure and --skip-tls-verify ?

tejal29 on 18 Sep 2020

Hey @CeadeS could you try again with gcr.io/kaniko-project/executor: 51734fc3a33e04f113487853d118608ba6ff2b81? I'm wondering if #685 will fix your issue.

I was hitting the same issue and that image 51734fc3a33e04f113487853d118608ba6ff2b81 fixed the problem!

   steps:
     - name: build-and-push
       # https://github.com/GoogleContainerTools/kaniko/issues/702
       image: gcr.io/kaniko-project/executor:51734fc3a33e04f113487853d118608ba6ff2b81
       #image: gcr.io/kaniko-project/executor:latest
       #image: gcr.io/kaniko-project/executor:debug
       # specifying DOCKER_CONFIG is required to allow kaniko to detect docker credential
       env:
         - name: "DOCKER_CONFIG"
           value: "/tekton/home/.docker/"
       command:
         - /kaniko/executor
       args:
         - --dockerfile=$(params.pathToDockerFile)
         - --destination=$(params.registryURL)/$(params.imageOwner)/$(params.imageName):$(params.imageTag)
         - --context=$(params.pathToContext)
         - --insecure
         - --skip-tls-verify
         - --skip-tls-verify-pull
         - --insecure-pull