From 21c4549fc88804cbd8be1dee057b96d187173d2d Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 24 May 2018 12:18:42 -0700 Subject: [PATCH] added instructions in air to run the install commands. --- .../v2.x/en/installation/air-gap-installation/_index.md | 4 ++++ 1 file changed, 4 insertions(+) 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 2387a5081d2..3560b81f9c4 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 @@ -34,6 +34,8 @@ We will cover two scenarios: 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`. +5. Complete installation of Rancher using the instructions in [Single Node Install]({{< baseurl >}}/rancher/v2.x/en/installation/single-node-install/). + #### Scenario 2: You have one host that can access both DockerHub and your private registry. ![Scenario2]({{< baseurl >}}/img/rancher/airgap/privateregistrypushpull.svg) @@ -53,6 +55,8 @@ for IMAGE in $IMAGES; do docker push registry.yourdomain.com:5000/$IMAGE done ``` +3. Complete installation of Rancher using the instructions in [Single Node Install]({{< baseurl >}}/rancher/v2.x/en/installation/single-node-install/). + ### Configuring Rancher to use the private registry