Deploying a private Docker registry

You can deploy a private Docker registry to store images for use by Docker containers.

Before you begin

Note: Docker Private Registry pattern is deprecated in Version 2.3.3.4 and later. The same feature can now be used from the Cloud Paks Docker Private Registry pattern by selecting Registry Node > import_ocp_docker_images > ocpversions > None in the Deploy page of the IBM® Cloud Pak System user interface.
The Docker Pattern Type must be installed and enabled.

Procedure

  1. Log on to Cloud Pak System.
  2. Click Patterns > Virtual System Patterns.
  3. Select the Docker Private Registry pattern.
  4. Click Open.
  5. Confirm that the Core OS component is set to a Red Hat® Enterprise Linux® (RHEL) 7.x or Red Hat Enterprise Linux (RHEL) 8.x virtual image. If needed, change the virtual image.
    Note: Docker pattern 1.0.15.1 supports only Red Hat Enterprise Linux (RHEL) 7.x or Red Hat Enterprise Linux (RHEL) 8.4. RHEL 6.x is no longer supported. You must select only the RHEL 7.9 or the RHEL 8.4 image. If you are on 2.3.3.6, Docker pattern 1.0.15.4 supports Red Hat Enterprise Linux (RHEL) 8.6. If you are on 2.3.3.6 interim fix, Docker pattern 1.0.15.5 supports Red Hat Enterprise Linux (RHEL) 8.6. You must select the RHEL 8.6 image.
  6. Save your changes.
  7. Deploy the pattern. For more information about deploying patterns, see the Related Tasks.
    Important: Be sure that you configure SSH access when you deploy the pattern. You might need SSH to manage the Docker registry.

What to do next

Configure the Docker system plug-in with the details for the Docker registry so that it can be referenced by patterns.

Connect to your Docker registry by using SSH. You can use Docker commands to add Docker images to the Docker registry and work with existing Docker images. For more information about Docker commands, see the Docker documentation.

The deployed private Docker registry is not secure by default. If you want to protect the registry with enhanced security features, see the Docker documentation.