Skip to content
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

Builder not getting configured with private docker repo #1568

Closed
imasood90 opened this issue Jun 25, 2020 · 1 comment
Closed

Builder not getting configured with private docker repo #1568

imasood90 opened this issue Jun 25, 2020 · 1 comment
Labels
area/build-operator Related to the internal image build operator

Comments

@imasood90
Copy link

The kamel has been initialled with the private docker repository and with private maven repo. But with kamel run is executed the logs displayed the builder tries to get image from public docker repos rather than private one.

Following command is used :
**kamel install --registry docker-regsrv.de.stihl-dns.net:8080 --registry-secret regcred --maven-settings=configmap:maven-settings/maven_settings.xml **

Error logs from builder:

STEP 1: FROM adoptopenjdk/openjdk11:slim
error creating build container: The following failures happened while trying to pull image specified by "adoptopenjdk/openjdk11:slim" based on search registries in /etc/containers/registries.conf:

  • "localhost/adoptopenjdk/openjdk11:slim": Error initializing source docker://localhost/adoptopenjdk/openjdk11:slim: error pinging docker registry localhost: Get https://localhost/v2/: dial tcp 127.0.0.1:443: connect: connection refused
  • "docker.io/adoptopenjdk/openjdk11:slim": Error initializing source docker://adoptopenjdk/openjdk11:slim: error pinging docker registry registry-1.docker.io: Get https://registry-1.docker.io/v2/: dial tcp 3.223.220.229:443: connect: connection refused
  • "registry.fedoraproject.org/adoptopenjdk/openjdk11:slim": Error initializing source docker://registry.fedoraproject.org/adoptopenjdk/openjdk11:slim: error pinging docker registry registry.fedoraproject.org: Get https://registry.fedoraproject.org/v2/: dial tcp 38.145.60.20:443: connect: connection refused
  • "registry.access.redhat.com/adoptopenjdk/openjdk11:slim": Error initializing source docker://registry.access.redhat.com/adoptopenjdk/openjdk11:slim: error pinging docker registry registry.access.redhat.com: Get https://registry.access.redhat.com/v2/: dial tcp 2.16.100.66:443: i/o timeout
  • "registry.centos.org/adoptopenjdk/openjdk11:slim": Error initializing source docker://registry.centos.org/adoptopenjdk/openjdk11:slim: error pinging docker registry registry.centos.org: Get https://registry.centos.org/v2/: dial tcp 8.43.84.200:443: connect: connection refused
  • "quay.io/adoptopenjdk/openjdk11:slim": Error initializing source docker://quay.io/adoptopenjdk/openjdk11:slim: error pinging docker registry quay.io: Get https://quay.io/v2/: dial tcp 18.205.55.240:443: connect: connection refused
    level=error msg="exit status 1"
@astefanutti astefanutti added the area/build-operator Related to the internal image build operator label Jul 21, 2020
@astefanutti
Copy link
Member

The base image used to build the Integration containers must point to the internal registry. Otherwise, it defaults to adoptopenjdk/openjdk11:slim, which explains why it searches it by relying on the content of /etc/containers/registries.conf.

This can be changed with the --base-image option of the kamel install command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-operator Related to the internal image build operator
Projects
None yet
Development

No branches or pull requests

2 participants