Important:

IBM Cloud Pak® for Data Version 4.8 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.
Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.8 reaches end of support. For more information, see Upgrading from IBM Cloud Pak for Data Version 4.8 to IBM Software Hub Version 5.1.

Creating a custom image

After you have downloaded the image for the runtime that you want to customize, you can build a new custom image by adding your customizations to the downloaded image. You do this by adding your customizations to a Dockerfile.

You can build a custom image on any server or workstation running Docker, Podman or Skopeo. The custom image does not have to be created on Red Hat Enterprise Linux.

You can customize these types of images:

  • Jupyter notebook images
  • JupyterLab image
  • RStudio image For details, refer to the following steps.

To customize an image:

  1. Add your customizations to the Dockerfile. To get started based on recommended best practices and methods for building efficient images, see Adding customizations to images.

    The image is built by reading the instructions from the Dockerfile. The Dockerfile takes as input the base-image-tag argument with the name of base image that you downloaded as its value.

    You should use the example commands that Dockerfile provides to add your customizations to avoid introducing a breaking change, which could prevent the new image from working in Cloud Pak for Data.

  2. Build the new image. The command shows building a new image based on wslocal-runtime-241-py@sha256:f21b54dee335c9a39de5980a41ac2a422a2bda8820b91da005dba53ba5857434. The value of <your_image_registry_location> is the URL to the external registry that was used during the installation of Cloud Pak for Data.

    • For Docker, enter:

      docker build -t <new-image-name>:<new-image-tag> --build-arg base_image_tag= <your_image_registry_location>/wslocal-runtime-241-py@sha256:f21b54dee335c9a39de5980a41ac2a422a2bda8820b91da005dba53ba5857434 -f <path_to_dockerfile>

    • For Buildah, enter:

      buildah bud -t <new-image-name>:<new-image-tag> --build-arg base_image_tag= <your_image_registry_location>/wslocal-runtime-241-py@sha256:f21b54dee335c9a39de5980a41ac2a422a2bda8820b91da005dba53ba5857434 -f <path_to_dockerfile>

      Make sure that you use the correct image and directory setup.

Parent topic: Building custom images