Pulling images from IBM Entitled Registry to a local registry

Edit online
Obtain the IBM® Sterling Intelligent Promising container images from IBM Entitled Registry to push them into your cluster.

About this task

To pull the IBM Sterling Intelligent Promising container images from IBM Entitled Registry you must supply your entitlement key.

Procedure

  1. Obtain an entitlement key from IBM Container Software Library by using your IBMid and password that are associated with the entitled software.

    If you are not directed to the Entitlement page, click View library and click Get entitlement key.

  2. Click Copy key to copy the generated entitlement key and save the entitlement key to a safe location for later use.
  3. Optional: Click View library to verify the validity of the entitlement key.

    You can view the list of products that you are entitled to. If IBM Sterling Intelligent Promising is not listed or if the View library link is disabled it indicates that the identity with which you are logged in to the container library does not have an entitlement for IBM Sterling Intelligent Promising. In this case, the entitlement key is not valid for installing the software.

  4. Configure the entitled registry information by completing the following steps:
    1. Run export commands to set ENTITLED_REGISTRY to cp.icr.io.
    2. Set ENTITLED_REGISTRY_USER to cp.
    3. Set ENTITLED_REGISTRY_KEY to the entitlement key that you have saved.
  5. Run the following command to log in to IBM Entitled Registry: 
    <containerization_tool> login "$ENTITLED_REGISTRY" -u "$ENTITLED_REGISTRY_USER" -p "$ENTITLED_REGISTRY_KEY"

    Here, <containerization_tool> refers to buildah, docker, or podman based on your platform.

    For example, buildah login "$ENTITLED_REGISTRY" -u "$ENTITLED_REGISTRY_USER" -p "$ENTITLED_REGISTRY_KEY"

  6. Run the following command to pull the container images from IBM Entitled Registry:
     
    <containerization_tool> pull cp.icr.io/cp/ibm-oms-enterprise/<image_name>:<image_tag>-<cpu_architecture>
    Here,
    • <containerization_tool> refers to buildah, docker, or podman based on your platform.
    • <image_name> refers to name of the application image. For more information about the list of images, see Registry image names for IBM Sterling Intelligent Promising Standard edition.
    • <image_tag> refers to the supported image tag for the release.
    • <cpu_architecture> refers to the supported CPU architectures namely amd64 or ppc64le.
    For example, cp.icr.io/cp/ibm-oms-enterprise/sip-iv-audit:10.0.2309.1-amd64
  7. Push the images obtained from IBM Entitled Registry to your local registry.
  8. Pull the following images from the Red Hat registry.
    • registry.access.redhat.com/ubi8/ubi-minimal:latest
    • registry.access.redhat.com/ubi8/openjdk-11:latest
    • registry.access.redhat.com/ubi8/openssl:latest
  9. Push the images to your local registry with the following image names and tags.
      • <local registry>/ubi8/ubi-minimal:latest
      • <local registry>/ubi8/openjdk-11:latest
      • <local registry>/ubi8/openssl:latest