Deploying a private Docker registry

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

Before you begin

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 virtual image. If needed, change the virtual image.
    Note: Docker CE 17.09.1 supports only Red Hat Enterprise Linux (RHEL) 7. Therefore, be sure that the operating system node is a RHEL 7 image when you build a virtual system pattern with a Docker container. If a RHEL 6 image is selected, the virtual system pattern deployment fails.

    The Docker pattern installs Docker CE 17.09.1. All required dependencies are installed on the RHEL 7.3 image, version 3.0.9.0, which is available with the Cloud Pak System group content (sometimes referred to as default data). If you use a different RHEL 7 image, some of the Docker prerequisites, such as libseccomp package, might not be available. You can still use these images if you have a Red Hat Satellite server that is deployed in the same environment profile as the deployed Docker pattern instance. The Docker pattern tries to install the missing packages by using the Red Hat Satellite server.

  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.