Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerProtect Cyber Recovery 19.13 Installation Guide

PDF

Migrating to Docker Community Edition

Migrate Docker Enterprise Edition (EE) from Mirantes to Docker Community Edition (CE).

Prerequisites

  • Docker EE is running on the Cyber Recovery deployment.
  • The current Cyber Recovery deployment is running version 19.13.
  • The Docker CE RPM download package is available.
  • The images that are present for the deployment are recorded for verification of the installed images during the migration procedure.

About this task

NOTE: Docker Enterprise Edition (EE) has been acquired by Mirantis and is now known as Mirantis Kubernetes Engine. For information about Mirantis Kubernetes Engine, see the Mirantis website.

Steps

  1. Create a backup copy of the existing deployment:
    # ./crsetup.sh --save
  2. Uninstall Docker EE:
    sudo yum -y remove docker-ee \ 
       docker-ee-cli \ 
       containerd.io  \ 
       container-selinux
    NOTE: Do not clean up Docker volumes and containers.
  3. Verify that Docker EE is removed:
    # docker version
    -bash: /usr/bin/docker: No such file or directory
     
    # docker ps
    -bash: /usr/bin/docker: No such file or directory
  4. Install Docker CE version 21.10 from the downloaded RPM package:
    yum install -y <docker-rpm-path>/containerd.io-1.6.6-3.1.el7.x86_64.rpm <docker-rpm-path>/docker-ce-20.10.17-3.el7.x86_64.rpm <docker-rpm-path>/docker-ce-cli-20.10.17-3.el7.x86_64.rpm <docker-rpm-path>/dockerce-rootless-extras-20.10.17-3.el7.x86_64.rpm <docker-rpm-path>/docker-scanplugin-0.17.0-3.el7.x86_64.rpm
    NOTE: For more information, go to https://docs.docker.com/engine/install/.
  5. Verify that the present Docker images match the images that you recorded before performing the migration:
    # docker images
  6. Verify that only the Cyber Recovery registry container is up and running:
    # docker ps
    CONTAINER ID IMAGE                               COMMAND                CREATED     STATUS        PORTS                       NNAMES
    7141b913f9b0 localhost:14779/cr_registry:2.8.1.4 "/entrypoint.sh /etc…" 3 hours ago Up 15 seconds 127.0.0.1:14779->5000/tcp   cr_registry
    
  7. Start all Cyber Recovery services and verify that all containers are up and running:
    # ./crsetup.sh --start
  8. Verify that the installation is successful by logging in to the Cyber Recovery UI.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\