Attention: This version of Event Streams has reached End of Support. For more information about supported versions, see the support matrix.

KafkaConnectS2I build fails in an air-gapped installation


The following error message is displayed when installing KafkaConnectS2I in an air-gapped environment:

unknown: unable to pull manifest from Get dial tcp: lookup on no such host


In an isolated system, there is no network access to the entitled image registry

Resolving the problem

To resolve the error, place the correct image into the cluster’s internal registry as follows.

Note: The <RELEASE_SHA> in the following instructions is the SHA output in the error message. In the example mentioned earlier, it is a508bbc97cba7643a521c772a5ade4bd20dfa169156cafd4fda4d0614b3ad61b

  1. Log in to the entitled registry:

    docker login

  2. Pull the image:

    docker pull<RELEASE_SHA>

  3. Tag the image:

    docker tag<RELEASE_SHA> default-route-openshift-image-registry.apps.<CLUSTER_NAME>/<NAMESPACE>/ibm-eventstreams-kafka:fix

  4. If not already done, expose the OpenShift Container Platform registry with the following command:

    oc patch --patch '{"spec":{"defaultRoute":true}}' --type=merge

  5. Log in to the OpenShift Container Platform registry:

    docker login -u any_value -p $(oc whoami -t) default-route-openshift-image-registry.apps.<CLUSTER_NAME>.

    Note: You might need to add your registry to your list of insecure registries in Docker.

  6. Push the tagged image:

    docker push default-route-openshift-image-registry.apps.<CLUSTER_NAME>/<NAMESPACE>/ibm-eventstreams-kafka:fix

  7. Modify the KafkaConnectS2I custom resource to add the image property under the spec:

        image:  image-registry.openshift-image-registry.svc:5000/<NAMESPACE>/ibm-eventstreams-kafka:fix

After following the steps, the correct image is added to the cluster’s internal registry, and the error message will no longer be displayed.