Cannot push to registry without port 80

[kimmoal]

Actual behavior

Somewhat similar to #1157 but I cannot seem to tell kaniko to use port 443 for pushing an image in any way.

Trying to push an image to an internal registry, I am getting an error:

Get "http://registry.internal.local/v2/": dial tcp 10.10.10.20:80: i/o timeout

Running internal Gitlab with runner + registry, no port 80 open (should not be a requirement IMHO)

Relevant lines from build log:

Using docker image sha256:ffca8c9f01a23d0886106b46f9bdd68dc5ca29d3377434bb69020df0cb2982a8 for gcr.io/kaniko-project/executor:debug with digest gcr.io/kaniko-project/executor@sha256:473d6dfb011c69f32192e668d86a47c0235791e7e857c870ad70c5e86ec07e8c ...

$ /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/$IMAGE_NAME/Dockerfile --destination $CI_REGISTRY/$CI_PROJECT_NAME/$IMAGE_NAME:latest

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 "registry.internal.local/testing/testimage:latest": creating push check transport for registry.internal.local failed: Get "http://registry.internal.local/v2/": dial tcp 10.10.10.20:80: i/o timeout

Tried to give the https endpoint in the configuration file in various ways, but could not get it to work:
CI_REGISTRY="registry.internal.local"
{\"auths\":{\"https://$CI_REGISTRY/v2/\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json

Expected behavior
I expect to be able to push to a private Gitlab registry without port 80

To Reproduce
Steps to reproduce the behavior:

1. execute kaniko in Gitlab CI with external runner
2. Build image in the runner
3. Try to push image to Gitlab registry

Additional Information

• Kaniko Image: gcr.io/kaniko-project/executor@sha256:473d6dfb011c69f32192e668d86a47c0235791e7e857c870ad70c5e86ec07e8c

Triage Notes for the Maintainers

Description	Yes/No
Please check if this a new feature you are proposing
Please check if the build works in docker but not in kaniko	- []
Please check if this error is seen when you use --cache flag	- []
Please check if your dockerfile is a multistage dockerfile	- []

[almorgv]

This might help #1157 (comment)

[kimmoal]

True, that helps, thanks! I would like to not skip the cert check, if possible

[fanjlii]

maybe cause by docket network mode, change to host works fine