Actual behavior
I am using gcr.io/kaniko-project/executor:debug image in a GitLab CI job to build docker images. The login/push to a private registry, which is not available in the dns, fails because of a "Bad Gateway" message. The registry needs to be accessed by dns name, because of its certificate.
Expected behavior
inserting the missing IP+Hostname to the local /etc/hosts will be recognized by kaniko executor:
echo "-ip- -hostname-" >> /etc/hosts
run the /kaniko/executor stuff
Description
Yes/No
Please check if this a new feature you are proposing
- [maybe]
Please check if the build works in docker but not in kaniko
- [ yes]
Please check if this error is seen when you use --cache flag
- [n/a ]
Please check if your dockerfile is a multistage dockerfile
Actual behavior I am using gcr.io/kaniko-project/executor:debug image in a GitLab CI job to build docker images. The login/push to a private registry, which is not available in the dns, fails because of a "Bad Gateway" message. The registry needs to be accessed by dns name, because of its certificate.
Expected behavior inserting the missing IP+Hostname to the local /etc/hosts will be recognized by kaniko executor:
run the /kaniko/executor stuff
--cache
flag