Install MSR¶

Hardware and Software requirements¶

You can install MSR on-premises or on a cloud provider. To install MSR, all nodes must:

• Be a worker node managed by MKE (Mirantis Kubernetes Engine). See Compatibility Matrix for version compatibility.
• Have a fixed hostname.

Ports used¶

When installing MSR on a node, make sure the following ports are open on that node:

These ports are configurable when installing MSR.

MKE Configuration¶

When installing or backing up MSR on a MKE cluster, Administrators need to be able to deploy containers on MKE manager nodes or nodes running MSR. This setting can be adjusted in the MKE Settings menu.

The MSR installation or backup will fail with the following error message if Administrators are unable to deploy on MKE manager nodes or nodes running MSR.

Error response from daemon: {"message":"could not find any nodes on which
the container could be created"}

Compatibility and maintenance lifecycle¶

Docker Enterprise Edition is a software subscription that includes three products:

• Mirantis Container Runtime
• Mirantis Secure Registry
• Mirantis Kubernetes Engine

Learn more about the Maintenance Lifecycle for these products.

Step 1. Validate the system requirements¶

Before installing MSR, make sure your infrastructure meets the MSR system requirements that MSR needs to run.

Step 2. Install MKE¶

MSR requires Mirantis Kubernetes Engine (MKE) to run. If MKE is not yet installed, refer to install MKE for production.

MKE and MSR must not be installed on the same node, due to the potential for resource and port conflicts. Instead, install MSR on worker nodes that will be managed by MKE. Note also that MSR cannot be installed on a standalone Mirantis Container Runtime.

Step 3. Install MSR¶

1. Once MKE is installed, navigate to the MKE web interface as an admin. Expand your profile on the left navigation pane, and select Admin Settings > Mirantis Secure Registry.

   

2. After you configure all the options, you should see a Docker CLI command that you can use to install MSR. Before you run the command, take note of the --dtr-external-url parameter:

   $ docker run -it --rm \
     docker/dtr:2.7.5 install \
     --dtr-external-url <msr.example.com> \
     --ucp-node <mke-node-name> \
     --ucp-username admin \
     --ucp-url <mke-url>
   

   If you want to point this parameter to a load balancer that uses HTTP for health probes over port 80 or 443, temporarily reconfigure the load balancer to use TCP over a known open port. Once MSR is installed, you can configure the load balancer however you need to.

3. Run the MSR install command on any node connected to the MKE cluster, and with the Mirantis Container Runtime installed. MSR will not be installed on the node you run the install command on. MSR will be installed on the MKE worker defined by the --ucp-node flag.

   For example, you could SSH into a MKE node and run the MSR install command from there. Running the installation command in interactive TTY or -it mode means you will be prompted for any required additional information.

   Here are some useful options you can set during installation:

   • To install a specific version of MSR, replace 2.7.6 with your desired version in the installation command above. Find all MSR versions in the Mirantis Secure Registry release notes.
   • MSR is deployed with self-signed certificates by default, so MKE might not be able to pull images from MSR. Use the --dtr-external-url <msr-domain>:<port> optional flag during installation, or during a reconfiguration, so that MKE is automatically reconfigured to trust MSR.
   • With MSR 2.7, you can enable browser authentication via client certificates at install time. This bypasses the MSR login page and hides the logout button, thereby skipping the need for entering your username and password.

4. Verify that MSR is installed. Either:

   • See https://<mke-fqdn>/manage/settings/msr, or;
   • Navigate to Admin Settings > Mirantis Secure Registry from the MKE web UI. Under the hood, MKE modifies /etc/docker/certs.d for each host and adds MSR’s CA certificate. MKE can then pull images from MSR because the Mirantis Container Runtime for each node in the MKE swarm has been configured to trust MSR.

5. Reconfigure your load balancer back to your desired protocol and port.

Step 4. Check that MSR is running¶

1. In your browser, navigate to the MKE web interface.

2. Select Shared Resources > Stacks from the left navigation pane. You should see MSR listed as a stack.

3. To verify that MSR is accessible from the browser, enter your MSR IP address or FQDN on the address bar. Since HSTS (HTTP Strict-Transport-Security) header is included in all API responses, make sure to specify the FQDN (Fully Qualified Domain Name) of your MSR prefixed with https://, or your browser may refuse to load the web interface.

   

Step 5. Configure MSR¶

After installing MSR, you should configure:

• The certificates used for TLS communication. Learn more.
• The storage back end to store the Docker images. Learn more.

Step 6. Test pushing and pulling¶

Now that you have a working installation of MSR, you should test that you can push and pull images:

• Configure your local MCR
• Create a repository
• Push and pull images

Step 7. Join replicas to the cluster¶

This step is optional.

To set up MSR for high availability, you can add more replicas to your MSR cluster. Adding more replicas allows you to load-balance requests across all replicas, and keep MSR working if a replica fails.

For high-availability, you should set 3 or 5 MSR replicas. The replica nodes also need to be managed by the same MKE.

To add replicas to a MSR cluster, use the join command.

1. Load your MKE user bundle.

2. Run the join command.

   docker run -it --rm \
     docker/dtr:2.7.6 join \
     --ucp-node <mke-node-name> \
     --ucp-insecure-tls
   

   Caution

   –ucp-node

   The <mke-node-name> following the --ucp-node flag is the target node to install the MSR replica. This is NOT the MKE Manager URL.

   When you join a replica to a MSR cluster, you need to specify the ID of a replica that is already part of the cluster. You can find an existing replica ID by going to the Shared Resources > Stacks page on MKE.

3. Check that all replicas are running.

   In your browser, navigate to MKE’s web interface. Select Shared Resources > Stacks. All replicas should be displayed.

   

Versions available¶

Download the offline package¶

Use a computer with internet access to download a package with all MSR images:

$ wget <package-url> -O dtr.tar.gz

Now that you have the package in your local machine, you can transfer it to the machines where you want to install MSR.

For each machine where you want to install MSR:

1. Copy the MSR package to that machine.

   $ scp dtr.tar.gz <user>@<host>
   

2. Use SSH to log in to the hosts where you transferred the package.

3. Load the MSR images.

   Once the package is transferred to the hosts, you can use the docker load command to load the Docker images from the tar archive:

   $ docker load -i dtr.tar.gz
   

Install MSR¶

Now that the offline hosts have all the images needed to install MSR, you can install MSR on that host.

DTR 2.5 to MSR 2.6 upgrade¶

Minor upgrade¶

Before starting the upgrade, confirm that:

• The version of MKE in use is supported by the upgrade version of MSR. Check the compatibility matrix.
• The MSR backup is recent.
• Docker content trust in MKE is disabled.
• All system requirements are met.

Step 2. Upgrade MSR¶

Pull the latest version of MSR:

docker pull docker/dtr:2.7.6

Confirm that at least 16GB RAM is available on the node on which you are running the upgrade. If the MSR node does not have access to the Internet, follow the Install MSR offline to get the images.

Once you have the latest image on your machine (and the images on the target nodes, if upgrading offline), run the upgrade command.

Note

The upgrade command can be run from any available node, as MKE is aware of which worker nodes have replicas.

docker run -it --rm \
  docker/dtr:2.7.6 upgrade

By default, the upgrade command runs in interactive mode and prompts for any necessary information. You can also check the upgrade reference page for other existing flags. If you are performing the upgrade on an existing replica, pass the --existing-replica-id flag.

The upgrade command will start replacing every container in your MSR cluster, one replica at a time. It will also perform certain data migrations. If anything fails or the upgrade is interrupted for any reason, rerun the upgrade command (the upgrade will resume from the point of interruption).

Metadata Store Migration¶

When upgrading from 2.5 to 2.6, the system will run a metadatastoremigration job following a successful upgrade. This involves migrating the blob links for your images, which is necessary for online garbage collection. With 2.6, you can log into the MSR web interface and navigate to System > Job Logs to check the status of the metadatastoremigration job. Refer to Audit Jobs via the Web Interface<msr-manage-jobs-audit-jobs-via-ui> for more details.

Garbage collection is disabled while the migration is running. In the case of a failed metadatastoremigration, the system will retry twice.

If the three attempts fail, it will be necessary to manually retrigger the metadatastoremigration job. To do this, send a POST request to the /api/v0/jobs endpoint:

curl https://<msr-external-url>/api/v0/jobs -X POST \
-u username:accesstoken -H 'Content-Type':'application/json' -d \
'{"action": "metadatastoremigration"}'

Alternatively, select API from the bottom left navigation pane of the MSR web interface and use the Swagger UI to send your API request.

Patch upgrade¶

A patch upgrade changes only the MSR containers and is always safer than a minor version upgrade. The command is the same as for a minor upgrade.

MSR cache upgrade¶

If you have previously deployed a cache, be sure to upgrade the node dedicated for your cache to keep it in sync with your upstream MSR replicas. This prevents authentication errors and other strange behaviors.

Download the vulnerability database¶

After upgrading MSR, it is necessary to redownload the vulnerability database. Learn how to update your vulnerability database.