IBM Support

Getting "om-app:10.0: image not known" error while executing the generateImages.sh script

Troubleshooting


Problem

When running the command "./generateImages.sh --MODE=app,agent --DEV_MODE=true", getting below error:

STEP 1/22: FROM ibmcom/websphere-liberty:21.0.0.3-kernel-java8-ibmjava-ubi

Resolving "ibmcom/websphere-liberty" using unqualified-search registries (/etc/containers/registries.conf)

Trying to pull registry.fedoraproject.org/ibmcom/websphere-liberty:21.0.0.3-kernel-java8-ibmjava-ubi...

Trying to pull registry.access.redhat.com/ibmcom/websphere-liberty:21.0.0.3-kernel-java8-ibmjava-ubi...

Trying to pull registry.centos.org/ibmcom/websphere-liberty:21.0.0.3-kernel-java8-ibmjava-ubi...

Trying to pull docker.io/ibmcom/websphere-liberty:21.0.0.3-kernel-java8-ibmjava-ubi...

error creating build container: 4 errors occurred while pulling:

* initializing source docker://registry.fedoraproject.org/ibmcom/websphere-liberty:21.0.0.3-kernel-java8-ibmjava-ubi: reading manifest 21.0.0.3-kernel-java8-ibmjava-ubi in registry.fedoraproject.org/ibmcom/websphere-liberty: manifest unknown: manifest unknown

* initializing source docker://registry.access.redhat.com/ibmcom/websphere-liberty:21.0.0.3-kernel-java8-ibmjava-ubi: reading manifest 21.0.0.3-kernel-java8-ibmjava-ubi in registry.access.redhat.com/ibmcom/websphere-liberty: name unknown: Repo not found

* initializing source docker://registry.centos.org/ibmcom/websphere-liberty:21.0.0.3-kernel-java8-ibmjava-ubi: pinging container registry registry.centos.org: Get "https://registry.centos.org/v2/": dial tcp: lookup registry.centos.org on 9.30.99.253:53: no such host

* initializing source docker://ibmcom/websphere-liberty:21.0.0.3-kernel-java8-ibmjava-ubi: reading manifest 21.0.0.3-kernel-java8-ibmjava-ubi in docker.io/ibmcom/websphere-liberty: errors:

denied: requested access to the resource is denied

unauthorized: authentication required

Tue Apr 30 08:06:15 UTC 2024

Build image from dockerfile

Copying Dockerfile to context and using APP_DF==/opt/ssfs/runtime/external_deployments_imagebuild/build_context/Dockerfile.om-app

STEP 1/3: FROM localhost/om-app-libs:10.0

Trying to pull localhost/om-app-libs:10.0...

time="2024-04-30T08:06:15Z" level=warning msg="failed, retrying in 2s ... (1/3). Error: initializing source docker://localhost/om-app-libs:10.0: pinging container registry localhost: Get \"https://localhost/v2/\": dial tcp 127.0.0.1:443: connect: connection refused"

time="2024-04-30T08:06:17Z" level=warning msg="failed, retrying in 2s ... (2/3). Error: initializing source docker://localhost/om-app-libs:10.0: pinging container registry localhost: Get \"https://localhost/v2/\": dial tcp 127.0.0.1:443: connect: connection refused"

time="2024-04-30T08:06:19Z" level=warning msg="failed, retrying in 2s ... (3/3). Error: initializing source docker://localhost/om-app-libs:10.0: pinging container registry localhost: Get \"https://localhost/v2/\": dial tcp 127.0.0.1:443: connect: connection refused"

error creating build container: initializing source docker://localhost/om-app-libs:10.0: pinging container registry localhost: Get "https://localhost/v2/": dial tcp 127.0.0.1:443: connect: connection refused

om-app:10.0: image not known

Saving app image tar ...

Tue Apr 30 08:06:21 UTC 2024

error pushing image "om-app:10.0" to "docker-archive:/opt/ssfs/runtime/../om-app_10.0.tar:localhost/om-app:10.0": om-app:10.0: image not known

./generateImages.sh: line 359: /opt/ssfs/runtime/../om-app_10.0.tar: No such file or directory

Tue Apr 30 08:06:26 UTC 2024

Cause

The issue occurs because the "om-app" image resides in a repository that is not locally available. It needs to be pulled from "ibmcom/websphere-liberty:21.0.0.3-kernel-java8-ibmjava-ubi", which requires authentication within the container.

Resolving The Problem

To resolve this issue, execute the following "buildah" command within the container before running the "generateImages.sh" script:

buildah login --username your_username --password your_password docker.io

This command will authenticate the necessary registry, allowing the image to be pulled successfully and resolving the issue with the "generateImages.sh" script.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"ARM Category":[{"code":"a8m50000000CbuEAAS","label":"Archive (DO NOT USE)-\u003ESterling Order Management System"}],"ARM Case Number":"TS016113519","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
20 September 2024

UID

ibm17155023

Page Feedback