diff --git a/content/rancher/v2.x/en/installation/air-gap-installation/_index.md b/content/rancher/v2.x/en/installation/air-gap-installation/_index.md index 9605122ce8a..19d83c0038e 100644 --- a/content/rancher/v2.x/en/installation/air-gap-installation/_index.md +++ b/content/rancher/v2.x/en/installation/air-gap-installation/_index.md @@ -1,339 +1,26 @@ --- -title: Preparing for Air Gap Install +title: Air Gap Install weight: 300 --- -Rancher supports installing from a private registry. In every [release](https://github.com/rancher/rancher/releases), we provide you with the needed Docker images and scripts to mirror those images to your own registry. The Docker images are used when nodes are added to a cluster, or when you enable features like pipelines or logging. +In environments where security is high priority, you can set up Rancher in an air gap configuration. Air gap installs are more secure than standard single-node or HA deployments because the network that runs Rancher is disconnected from the Internet, reducing your security surface area. ->**Prerequisite:** It is assumed you either have your own private registry or other means of distributing docker images to your machine. If you need help with creating a private registry, please refer to the [Docker documentation for private registries](https://docs.docker.com/registry/). +## Prerequisites ->**Note:** In Rancher v2.0.x, registries with authentication are not supported for installing from a private registry. The Docker images can only be pulled from a registry without authentication enabled. This limitation only applies to Docker images. +Rancher supports air gap installs using a private registry. You must have your own private registry or other means of distributing docker images to your machine. If you need help with creating a private registry, please refer to the [Docker documentation for private registries](https://docs.docker.com/registry/). -## Release Files +In every [release](https://github.com/rancher/rancher/releases), we provide you with the needed Docker images and scripts to mirror those images to your own registry. The Docker images are used when nodes are added to a cluster, or when you enable features like pipelines or logging. -* **rancher-images.txt**: Contains all images needed for that release. -* **rancher-save-images.sh**: This script will pull all needed images from DockerHub, and save all of the images as a compressed file called `rancher-images.tar.gz`. This file can be transferred to your on-premise host that can access your private registry. -* **rancher-load-images.sh**: This script will load images from rancher-images.tar.gz and push them to your private registry. You have to supply the hostname of your private registry as first argument to the script.
`rancher-load-images.sh registry.yourdomain.com:5000` +## Caveats -## Making the Rancher Images Available +In Rancher v2.0.x, registries with authentication are not supported for installing from a private registry. The Docker images can only be pulled from a registry without authentication enabled. This limitation only applies to Docker images. -We will cover two scenarios: +## Air Gap Installation Outline -* **Scenario 1**: You have a node that can access DockerHub to pull and save the images, and a separate node(s) that access your private registry to push the images. -* **Scenario 2**: You have node(s) that can access both DockerHub and your private registry. +While installing Rancher in an air gap configuration, you'll complete several different tasks. -### Scenario 1: A Node that Can Access DockerHub, Separate Node(s) That Can Access the Private Registry +- [1—Preparing the Private Registry]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/prepare-private-reg/) +- [2—Installing Rancher]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/) +- [3—Configuring Rancher for the Private Registry]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/config-rancher-for-private-reg/) -![Scenario1]({{< baseurl >}}/img/rancher/airgap/privateregistry.svg) - -1. Browse to the release page of your version of Rancher (e.g. `https://github.com/rancher/rancher/releases/tag/v2.0.0`) and download `rancher-save-images.sh` and `rancher-load-images.sh`. - -2. Transfer and run `rancher-save-images.sh` on the host the can access DockerHub. This will require at least 20GB of disk space. - -3. Transfer the output file from step 2 (`rancher-images.tar.gz`) to the host that can access the private registry. - -4. Transfer and run `rancher-load-images.sh` on the host that can access the private registry. It should be run in the same directory as `rancher-images.tar.gz`. - -### Scenario 2: You have node(s) that can access both DockerHub and your private registry. - -![Scenario2]({{< baseurl >}}/img/rancher/airgap/privateregistrypushpull.svg) - -1. Browse to the release page of your version of Rancher (e.g. `https://github.com/rancher/rancher/releases/tag/v2.0.0`) and download `rancher-images.txt`. - -2. Pull all the images present in `rancher-images.txt`, re-tag each image with the location of your registry, and push the image to the registry. This will require at least 20GB of disk space. See an example script below: - ``` - #!/bin/sh - IMAGES=`curl -s -L https://github.com/rancher/rancher/releases/download/v2.0.0/rancher-images.txt` - for IMAGE in $IMAGES; do - until docker inspect $IMAGE > /dev/null 2>&1; do - docker pull $IMAGE - done - docker tag $IMAGE /$IMAGE - docker push /$IMAGE - done - ``` - -## Completing the Rancher Installation - -After your private registry is setup on all node(s) for your Rancher installation, complete your Rancher installation. - -### Single Node Install - -Complete installation of Rancher using the instructions in [Single Node Install]({{< baseurl >}}/rancher/v2.x/en/installation/single-node-install/). - ->**Note:** -> When completing [Single Node Install]({{< baseurl >}}/rancher/v2.x/en/installation/single-node-install/), prepend your private registry URL to the image when running the `docker run` command. -> -> Example: -> ``` -> docker run -d --restart=unless-stopped \ -> -p 80:80 -p 443:443 \ -> /rancher/rancher:latest - ``` - -## Configuring Rancher to Use the Private Registry - -Rancher needs to be configured to use the private registry as source for the needed images. - -1. Go into the **Settings** view. - - ![Settings]({{< baseurl >}}/img/rancher/airgap/settings.png) - -2. Look for the setting called `system-default-registry` and choose **Edit**. - - ![Edit]({{< baseurl >}}/img/rancher/airgap/edit-system-default-registry.png) - -3. Change the value to your registry (e.g. `registry.yourdomain.com:port`). Do not prefix the registry with `http://` or `https://`. - - ![Save]({{< baseurl >}}/img/rancher/airgap/enter-system-default-registry.png) - - ->**Note:** If you want to configure the setting when starting the rancher/rancher container, you can use the environment variable `CATTLE_SYSTEM_DEFAULT_REGISTRY`. -> -> Example: -> ``` -docker run -d --restart=unless-stopped \ - -p 80:80 -p 443:443 \ - -e CATTLE_SYSTEM_DEFAULT_REGISTRY= \ - /rancher/rancher:v2.0.0 -``` - -You can install Rancher in an air gap environment in a high availability configuration. - -## HA Air Gap Install Outline - -Deployment of Rancher in a high-availability configuration within an air gap environment is a multistep process. - - - - -- [1—Gather Images](#1gather-images) -- [2—Populate the Registry](#2populate-the-registry) -- [3—Run RKE with Private Registry Options](#3run-rke-with-private-registry-options) -- [4—Install Helm (tiller)](#4install-helm-tiller) -- [5—Install Rancher](#5install-rancher) - - - -## 1—Gather Images - -To get started with an HA install within an air gap environment, download the software and files that you'll use for installation. - -1. Download the four images required to populate your private Docker registry, which will be used to launch Rancher Server. - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DownloadDescription
RKE - A list of RKE images that are required can be compiled by running the following command. - 
rke config --system-images
-
rancher-images.txt Rancher has additional images it uses when installing clusters. These images are listed in rancher-images.txt, which can be found at GitHub Releases page for rancher/rancher.
Helm tiller Image - You can discover the tiller image compatible with your installed version of helm with the command below. - 
helm init --dry-run --debug | grep image: | awk '{print $2}'
-
cert-manager ImageRancher uses the cert-manager project to issue self-singed certificates for Rancher GUI/Agent access. You can inspect the cert-manager chart values.yaml to find the latest image and tag. - 
 helm inspect values stable/cert-manager
-        ...
-        image:
-          repository: quay.io/jetstack/cert-manager-controller
-          tag: v0.4.1
-        ...
-
- -1. From a system with internet access, use the shell script below to compile the images required by the latest Rancher release and write them to `images.txt` in the local directory. - - ```bash - #!/bin/bash - set -e - - # Collect images for Air Gap/Private Registry install - # Requires: - # rke - https://rancher.com/docs/rke/v0.1.x/en/installation/ - # helm - https://docs.helm.sh/using_helm/#installing-helm - # curl - # jq - - echo "RKE Images" - rke config --system-images 2>/dev/null > tmp-images.txt - - echo "Helm Tiller Image" - helm init --dry-run --debug | grep image: | awk '{print $2}' >> tmp-images.txt - - echo "Rancher Images" - latest_url=$(curl -sS "https://api.github.com/repos/rancher/rancher/releases/latest" | jq -r '.assets[]|select(.name=="rancher-images.txt")|.browser_download_url') - curl -sSL ${latest_url} >> tmp-images.txt - - echo "Cert-Manager Image" - cm_repo=$(helm inspect values stable/cert-manager | grep repository: | awk '{print $2}') - cm_tag=$(helm inspect values stable/cert-manager | grep tag: | awk '{print $2}') - echo "${cm_repo}:${cm_tag}" >> tmp-images.txt - - echo "Sort and uniq the images list" - cat tmp-images.txt | sort -u | uniq > images.txt - - # cleanup tmp file - rm tmp-images.txt - ``` - -## 2—Populate the Registry - -Each image in the list needs to be pulled from public registries, tagged with your private registry URL/path, and then pushed up to your private registry. - -1. Pull the images from public registries using the following command: - - ```plain - docker pull rancher/coreos-etcd:v3.1.12 - ``` - -1. Tag the images with your private registry URL and path: - - ```plain - docker tag rancher/coreos-etcd:v3.1.12 /rancher/coreos-etcd:v3.1.12 - ``` -1. Push the images to your private registry: - - ```plain - docker push /rancher/coreos-etcd:v3.1.12 - ``` - -1. Use the shell script below to to populate the private registry. This shell script can be used with a list of images (`images.txt`). To use this script, the system needs access to both the Internet and the private registry. - - ```bash - #!/bin/bash - - # Usage: - # ./populate-images.sh --registry my_registry.example.com --images ./images.txt - - POSITIONAL=() - while [[ $# -gt 0 ]] - do - key="$1" - - case $key in - -r|--registry) - reg="$2" - shift # past argument - shift # past value - ;; - -i|--images) - images="$2" - shift - shift - ;; - esac - done - - if [[ -z $reg ]]; then - echo "-r|--registry is required" - exit 1 - fi - - if [[ -z $images ]]; then - echo "-i|--images file is required" - exit 1 - fi - - echo "Log into Docker registry ${reg}" - docker login ${reg} - - for i in $(cat ${images}); do - docker pull ${i} - docker tag ${i} ${reg}/${i} - docker push ${reg}/${i} - done - ``` - -## 3—Run RKE with Private Registry Options - -Edit your `cluster.yaml` file, specifying your cluster nodes and your private registry. - -1. Edit `cluster.yaml`, specifying the nodes you created. Include the `private_registries:` block. Set `is_default: true` for the registry that you pushed the images to. - - nodes: - - address: 18.222.121.187 - internal_address: 172.31.7.22 - user: rancher - role: [ "controlplane", "etcd", "worker" ] - ssh_key_file: /home/user/.ssh/id_rsa - - address: 18.220.193.254 - internal_address: 172.31.13.132 - user: rancher - role: [ "controlplane", "etcd", "worker" ] - ssh_key_file: /home/user/.ssh/id_rsa - - address: 13.59.83.89 - internal_address: 172.31.3.216 - user: rancher - role: [ "controlplane", "etcd", "worker" ] - ssh_key_file: /home/user/.ssh/id_rsa - private_registries: - - url: my_registry.example.com - user: rancher - password: "*********" - is_default: true - - -1. Run RKE to set up your cluster using your private registry. - - ``` - rke up - ``` - -## 4—Install Helm (tiller) - -Install the Helm package manager. You'll use this software to install Rancher on the Kubernetes cluster you just set up. - -1. The `tiller` serviceAccount that the tiller deployment uses needs credentials to access your private registry. Set up the serviceAccount and RBAC permissions as depicted below. Then patch the service account to add the credentials. - - ``` - kubectl -n kube-system create serviceaccount tiller - kubectl create clusterrolebinding tiller \ - --clusterrole cluster-admin \ - --serviceaccount=kube-system:tiller - ``` - -1. Initialize Helm with the `tiller` image in your private registry. - - ``` - helm init --service-account tiller \ - --tiller-image user-ag-2-registry.rancher.space/gcr.io/kubernetes-helm/tiller:v2.10.0 - ``` - -## 5—Install Rancher - -Finally, we're ready to install Rancher. - -1. Install cert-manager, which automatically creates and handles certificates for your Rancher deployment. - - ``` - helm install stable/cert-manager --name cert-manager --namespace kube-system \ - --set image.repository=user-ag-2-registry.rancher.space/quay.io/jetstack/cert-manager-controller - ``` - -1. Install Rancher, setting the image source and imagePullSecrets options. - - ```plain - helm install rancher-stable/rancher --name rancher --namespace cattle-system \ - --set hostname=user-ag-2.rancher.space \ - --set rancherImage=user-ag-2-registry.rancher.space/rancher/rancher - ``` + +### [Next: Prepare the Private Registry]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/prepare-private-reg/) \ No newline at end of file diff --git a/content/rancher/v2.x/en/installation/air-gap-installation/config-rancher-for-private-reg/_index.md b/content/rancher/v2.x/en/installation/air-gap-installation/config-rancher-for-private-reg/_index.md new file mode 100644 index 00000000000..0a794b85f81 --- /dev/null +++ b/content/rancher/v2.x/en/installation/air-gap-installation/config-rancher-for-private-reg/_index.md @@ -0,0 +1,32 @@ +--- +title: 3—Configuring Rancher for the Private Registry +weight: 75 +aliases: +--- + +Rancher needs to be configured to use the private registry as source for the needed images. + +1. Go into the **Settings** view. + + ![Settings]({{< baseurl >}}/img/rancher/airgap/settings.png) + +2. Look for the setting called `system-default-registry` and choose **Edit**. + + ![Edit]({{< baseurl >}}/img/rancher/airgap/edit-system-default-registry.png) + +3. Change the value to your registry (e.g. `registry.yourdomain.com:port`). Do not prefix the registry with `http://` or `https://`. + + ![Save]({{< baseurl >}}/img/rancher/airgap/enter-system-default-registry.png) + + +>**Note:** If you want to configure the setting when starting the rancher/rancher container, you can use the environment variable `CATTLE_SYSTEM_DEFAULT_REGISTRY`. +> +> Example: +> ``` +docker run -d --restart=unless-stopped \ + -p 80:80 -p 443:443 \ + -e CATTLE_SYSTEM_DEFAULT_REGISTRY= \ + /rancher/rancher:v2.0.0 +``` + + diff --git a/content/rancher/v2.x/en/installation/air-gap-installation/install-rancher/_index.md b/content/rancher/v2.x/en/installation/air-gap-installation/install-rancher/_index.md new file mode 100644 index 00000000000..011c59ab297 --- /dev/null +++ b/content/rancher/v2.x/en/installation/air-gap-installation/install-rancher/_index.md @@ -0,0 +1,91 @@ +--- +title: 2—Installing Rancher +weight: 50 +aliases: +--- + +After your private registry is setup for your Rancher installation, complete that installation. Follow one of the procedures below based on the configuration in which you want to run Rancher. + + + +- [Single Node Install](#single-node-install) +- [High Availability Install](#high-availability-install) + + + +## Single Node Install + +To deploy Rancher on a single node in an air gap environment, follow the instructions in [Single Node Install]({{< baseurl >}}/rancher/v2.x/en/installation/single-node-install/). Parts of the install where you must complete a special action for air gap are flagged with a substitute step, which is listed in the subheading below. + + +### Add Private Registry URL to Run Command + +When you get [Choose an SSL Option and Install Rancher]({{< baseurl >}}/rancher/v2.x/en/installation/single-node/#2-choose-an-ssl-option-and-install-rancher), regardless of which install option you choose, prepend your Rancher image tag with your private registry URL (``), as shown in the example below. + +``` +docker run -d --restart=unless-stopped \ + -p 80:80 -p 443:443 \ + /rancher/rancher:latest +``` + +## High Availability Install + +To install Rancher in a high availability configuration within an air gap environment, follow the instructions in [High Availability Install]({{< baseurl >}}/rancher/v2.x/en/installation/ha). Parts of the install where you must complete a special action for air gap are flagged with substitute steps, which are listed in the subheadings below. + +### Add Private Registry to RKE YAML + +When you get to [Create the rancher-cluster.yml File]({{< baseurl >}}/rancher/v2.x/en/installation/ha/kubernetes-rke/#create-the-rancher-cluster-yml-file), replace its code sample with the one below, which adds the `private registries` block: + +```yaml +nodes: + - address: 18.222.121.187 + internal_address: 172.31.7.22 + user: rancher + role: [ "controlplane", "etcd", "worker" ] + ssh_key_file: /home/user/.ssh/id_rsa + - address: 18.220.193.254 + internal_address: 172.31.13.132 + user: rancher + role: [ "controlplane", "etcd", "worker" ] + ssh_key_file: /home/user/.ssh/id_rsa + - address: 13.59.83.89 + internal_address: 172.31.3.216 + user: rancher + role: [ "controlplane", "etcd", "worker" ] + ssh_key_file: /home/user/.ssh/id_rsa + private_registries: + - url: my_registry.example.com + user: rancher + password: "*********" + is_default: true +``` + +### Initialize Helm Using Private Registry + +When you get to [Helm Init]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-init/#helm-init), add your private registry in the step to initialize Helm, as shown below: + +``` +helm init --service-account tiller \ +--tiller-image user-ag-2-registry.rancher.space/gcr.io/kubernetes-helm/tiller:v2.10.0 +``` + +### Install cert-manager Using Private Registry + +When you get to [Install cert-manager]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/#install-cert-manager), replace the install commands provided with the one below: + +``` +helm install stable/cert-manager --name cert-manager --namespace kube-system \ +--set image.repository=user-ag-2-registry.rancher.space/quay.io/jetstack/cert-manager-controller +``` + +### Install Rancher Using Private Registry + +When you get to [Choose Your SSL Configuration]({{< baseurl >}}/rancher/v2.x/en/installation/ha/helm-rancher/#choose-your-ssl-configuration), set your `hostname` and `rancherImage`, adding your private registry's URL, as shown below: + +```plain +helm install rancher-stable/rancher --name rancher --namespace cattle-system \ +--set hostname=user-ag-2.rancher.space \ +--set rancherImage=user-ag-2-registry.rancher.space/rancher/rancher +``` + +### [Next: Configuring Rancher for the Private Registry]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/config-rancher-for-private-reg/) \ No newline at end of file diff --git a/content/rancher/v2.x/en/installation/air-gap-installation/prepare-private-reg/_index.md b/content/rancher/v2.x/en/installation/air-gap-installation/prepare-private-reg/_index.md new file mode 100644 index 00000000000..f17a2d6d909 --- /dev/null +++ b/content/rancher/v2.x/en/installation/air-gap-installation/prepare-private-reg/_index.md @@ -0,0 +1,147 @@ +--- +title: 1—Preparing the Private Registry +weight: 25 +aliases: +--- + +For the first part of your air gap install, you'll prepare your private registry for Rancher installation by downloading the Rancher release files, and then pushing them to your private registry. + +1. Browse to the [Rancher releases page](https://github.com/rancher/rancher/releases) and download the following files from the build with the `Latest release` tag. + + | Release File | Description | + | ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | `rancher-images.txt` | Contains all images needed to deploy the release. | + | `rancher-load-images.sh` | This script loads images from `rancher-images.tar.gz` and pushes them to your private registry. You have to supply the hostname of your private registry as first argument to the script.
`rancher-load-images.sh registry.yourdomain.com:5000` | + | `rancher-save-images.sh` | This script pulls all needed images from DockerHub and saves all of the images as a compressed file called `rancher-images.tar.gz`. This file can be transferred to your on-premise host that can access your private registry. | + + +1. **High Availablity Installs Only:** You need some additional software to complete installation in an air gap environment. Download the software in the table below. + + | Software | Description | + |----------|-------------| + | RKE | Rancher Kubernetes Engine (RKE) is Rancher's fast, light-weight Kubernetes installer. | + | Helm Image (tiller) | You can discover the tiller image compatible with your installed version of Helm. + | cert-manager | Rancher uses the [cert-manager](https://github.com/jetstack/cert-manager) project to issue self-singed certificates for Rancher GUI/Agent access. + +1. From a system with internet access, use the shell script below to compile the images required by the latest Rancher release and write them to `images.txt` in the local directory. + + ```bash + #!/bin/bash + set -e + + # Collect images for Air Gap/Private Registry install + # Requires: + # rke - https://rancher.com/docs/rke/v0.1.x/en/installation/ + # helm - https://docs.helm.sh/using_helm/#installing-helm + # curl + # jq + + echo "RKE Images" + rke config --system-images 2>/dev/null > tmp-images.txt + + echo "Helm Tiller Image" + helm init --dry-run --debug | grep image: | awk '{print $2}' >> tmp-images.txt + + echo "Rancher Images" + latest_url=$(curl -sS "https://api.github.com/repos/rancher/rancher/releases/latest" | jq -r '.assets[]|select(.name=="rancher-images.txt")|.browser_download_url') + curl -sSL ${latest_url} >> tmp-images.txt + + echo "Cert-Manager Image" + cm_repo=$(helm inspect values stable/cert-manager | grep repository: | awk '{print $2}') + cm_tag=$(helm inspect values stable/cert-manager | grep tag: | awk '{print $2}') + echo "${cm_repo}:${cm_tag}" >> tmp-images.txt + + echo "Sort and uniq the images list" + cat tmp-images.txt | sort -u | uniq > images.txt + + # cleanup tmp file + rm tmp-images.txt + ``` +
+1. Use the Rancher release that you just downloaded to populate your private registry with Rancher images. Use the scenario that best matches your use case. +
+{{% tabs %}} +{{% tab "Scenario 1" %}} +
+You have a node that can access DockerHub to pull and save the images, and a separate node(s) that access your private registry to push the images. + +![Scenario1]({{< baseurl >}}/img/rancher/airgap/privateregistry.svg) + +1. Browse to the release page of your version of Rancher (e.g. `https://github.com/rancher/rancher/releases/tag/v2.0.0`) and download `rancher-save-images.sh` and `rancher-load-images.sh`. + +2. Transfer and run `rancher-save-images.sh` on the host the can access DockerHub. This will require at least 20GB of disk space. + +3. Transfer the output file from step 2 (`rancher-images.tar.gz`) to the host that can access the private registry. + +4. Transfer and run `rancher-load-images.sh` on the host that can access the private registry. It should be run in the same directory as `rancher-images.tar.gz`. +{{% /tab %}} +{{% tab "Scenario 2" %}} +
+You have node(s) that can access both DockerHub and your private registry. +![Scenario2]({{< baseurl >}}/img/rancher/airgap/privateregistrypushpull.svg) + +1. Browse to the release page of your version of Rancher (e.g. `https://github.com/rancher/rancher/releases/tag/v2.0.0`) and download `rancher-images.txt`. + +2. Pull all the images present in `rancher-images.txt`, re-tag each image with the location of your registry, and push the image to the registry. This will require at least 20GB of disk space. See an example script below: + ``` + #!/bin/sh + IMAGES=`curl -s -L https://github.com/rancher/rancher/releases/download/v2.0.0/rancher-images.txt` + for IMAGE in $IMAGES; do + until docker inspect $IMAGE > /dev/null 2>&1; do + docker pull $IMAGE + done + docker tag $IMAGE /$IMAGE + docker push /$IMAGE + done + ``` +{{% /tab %}} +{{% /tabs %}} + +1. Use the shell script below to to populate the private registry. This shell script can be used with a list of images (`images.txt`). To use this script, the system needs access to both the Internet and the private registry. + + ```bash + #!/bin/bash + + # Usage: + # ./populate-images.sh --registry my_registry.example.com --images ./images.txt + + POSITIONAL=() + while [[ $# -gt 0 ]] + do + key="$1" + + case $key in + -r|--registry) + reg="$2" + shift # past argument + shift # past value + ;; + -i|--images) + images="$2" + shift + shift + ;; + esac + done + + if [[ -z $reg ]]; then + echo "-r|--registry is required" + exit 1 + fi + + if [[ -z $images ]]; then + echo "-i|--images file is required" + exit 1 + fi + + echo "Log into Docker registry ${reg}" + docker login ${reg} + + for i in $(cat ${images}); do + docker pull ${i} + docker tag ${i} ${reg}/${i} + docker push ${reg}/${i} + done + ``` + +### [Next: Install Rancher]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/) \ No newline at end of file