Prepare a container registry

A local container registry is used to store all images for the FTM solutions in your local environment. Create and then configure the container registry.

Create a container registry. It must meet the following requirements:
  • It must support Docker image manifest V2, schema 2. For more information, see the Docker Registry documentation.
  • It must be accessible from the Red Hat® OpenShift® cluster nodes.
  • It must have the username and password of a user who can write to the target registry.
  • It must have the username and password of a user who can read from the target registry that is on the Red Hat OpenShift cluster nodes.
  • It must allow path separators in the image name.

Configure the container registry

After you create the container registry, you must configure it.
  1. Create a separate registry namespace for each public registry source. The following list shows examples of the namespaces that you can use.
    cpopen
    Namespace to store all images from the icr.io/cpopen repository. The cpopen namespace is for all IBM® images that are publicly available and do not require credentials to pull.
    cp
    Namespace to store the IBM images from the cp.icr.io/cp repository. The cp namespace is for the images in the IBM Entitled Registry that require a product entitlement key and credentials to pull. The images for the FTM solutions are hosted on cp.icr.io/cp. For more information, see Installing the IBM Cloud Pak for Multicloud Management.
  2. Verify that each namespace meets the following requirements:
    • Supports auto-repository creation.
    • Has the credentials of a user who can write and create repositories. The bastion host uses these credentials.
    • Has the credentials of a user who can read all repositories. The Red Hat OpenShift cluster uses these credentials.