Downloading or listing IBM Cloud Pak for Watson AIOps images

You might need to download all of the container images for IBM Cloud Pak for Watson AIOps, for example, to copy them to an internal registry, scan them for vulnerabilities, or verify their signatures. This procedure describes how to download container images, although you may need to use different tools, depending on your particular environment.

  1. Follow the procedure in Installing IBM Cloud Pak for Watson AIOps in an air-gapped environment (offline) using a bastion host, up to and including the "Section 2 Download the CASE".

    These steps:

    • download the product CASE packages, which contain metadata for the container images required to deploy each capability. Each CASE package also contains the required scripts to mirror images to a private registry, and to configure the target cluster to use the private registry as a mirror.

    • generate comma-separated value (CSV) files listing the images for all capabilities (one CSV file is created for each capability and required dependencies). The CSV files, combined with your IBM Entitled Registry entitlement key, are used to download or mirror the images manually in the scripts below.

  2. Log in to your container tool to access the entitled registry, using the username cp and your entitlement key.

  3. Use a shell script to process all images from all capabilities supported on the target architecture.

    For example, for x86/amd64 architecture:

    tail -q -n +2 $HOME/offline/*-images.csv | while IFS="," read registry image_name tag digest mtype os arch variant insecure digest_source image_type groups; do
    if [[ "$arch" == "amd64" ]]; then
      docker pull "$registry/$image_name@$digest"
      docker tag "$registry/$image_name@$digest" "$registry/$image_name:$tag"

    Instead of docker, you can use alternative container tools such as podman or skopeo.

    • Use podman as a direct replacement for docker in the preceding commands.

    • Use one skopeocommand to replace the docker pull and docker tag commands. For example:

    skopeo copy --dest-tls-verify=false docker://$registry/$image_name@$digest docker-daemon:$registry/$image_name:$tag

    You can also use skopeo to save images to disk, or to copy them directly to another container registry.

    Note: If you need your clusters to access these images from a private registry, the image digests must be preserved. If this is your intention, IBM recommends using the procedure in Installing IBM Cloud Pak for Watson AIOps in an air-gapped environment (offline).