From 96de4a5fa30b0e45fff075672c756014c66588b3 Mon Sep 17 00:00:00 2001 From: Murali Paluru Date: Mon, 29 Jul 2019 12:27:00 -0700 Subject: [PATCH] changing alpine to busybox in instructions --- .../v2.x/en/backups/backups/single-node-backups/_index.md | 4 ++-- .../backups/restorations/single-node-restoration/_index.md | 6 +++--- .../en/upgrades/rollbacks/single-node-rollbacks/_index.md | 2 +- .../v2.x/en/upgrades/upgrades/single-node-upgrade/_index.md | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/content/rancher/v2.x/en/backups/backups/single-node-backups/_index.md b/content/rancher/v2.x/en/backups/backups/single-node-backups/_index.md index 2a7202ecb60..1ac352d5a3c 100644 --- a/content/rancher/v2.x/en/backups/backups/single-node-backups/_index.md +++ b/content/rancher/v2.x/en/backups/backups/single-node-backups/_index.md @@ -13,7 +13,7 @@ After completing your single node installation of Rancher, we recommend creating During the creation of your backup, you'll enter a series of commands, replacing placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (``). Here's an example of a command with a placeholder: ``` -docker run --volumes-from rancher-data- -v $PWD:/backup alpine tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher +docker run --volumes-from rancher-data- -v $PWD:/backup busybox tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher ``` In this command, `` is a placeholder for the date that the data container and backup were created. `9-27-18` for example. @@ -54,7 +54,7 @@ This procedure creates a backup that you can restore if Rancher encounters a dis 1. From the data container that you just created (`rancher-data-`), create a backup tarball (`rancher-data-backup--.tar.gz`). Use the following command, replacing each [placeholder](#before-you-start). ``` - docker run --volumes-from rancher-data- -v $PWD:/backup:z alpine tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher + docker run --volumes-from rancher-data- -v $PWD:/backup:z busybox tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher ``` **Step Result:** A stream of commands runs on the screen. diff --git a/content/rancher/v2.x/en/backups/restorations/single-node-restoration/_index.md b/content/rancher/v2.x/en/backups/restorations/single-node-restoration/_index.md index aacc1ea7d7c..00ecf9e2196 100644 --- a/content/rancher/v2.x/en/backups/restorations/single-node-restoration/_index.md +++ b/content/rancher/v2.x/en/backups/restorations/single-node-restoration/_index.md @@ -14,7 +14,7 @@ During restoration of your backup, you'll enter a series of commands, filling pl ``` docker run --volumes-from -v $PWD:/backup \ -alpine sh -c "rm /var/lib/rancher/* -rf && \ +busybox sh -c "rm /var/lib/rancher/* -rf && \ tar zxvf /backup/rancher-data-backup--" ``` @@ -56,7 +56,7 @@ Using a [backup]({{< baseurl >}}/rancher/v2.x/en/backups/backups/single-node-bac ``` docker run --volumes-from -v $PWD:/backup \ - alpine sh -c "rm /var/lib/rancher/* -rf && \ + busybox sh -c "rm /var/lib/rancher/* -rf && \ tar zxvf /backup/rancher-data-backup--.tar.gz" ``` @@ -68,4 +68,4 @@ Using a [backup]({{< baseurl >}}/rancher/v2.x/en/backups/backups/single-node-bac docker start ``` -1. Wait a few moments and then open Rancher in a web browser. Confirm that the restoration succeeded and that your data is restored. \ No newline at end of file +1. Wait a few moments and then open Rancher in a web browser. Confirm that the restoration succeeded and that your data is restored. diff --git a/content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md b/content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md index 9ee76e037da..f0304c2eb44 100644 --- a/content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md +++ b/content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md @@ -67,7 +67,7 @@ If you have issues upgrading Rancher, roll it back to its lastest known healthy ``` docker run --volumes-from rancher-data \ - -v $PWD:/backup alpine sh -c "rm /var/lib/rancher/* -rf \ + -v $PWD:/backup busybox sh -c "rm /var/lib/rancher/* -rf \ && tar zxvf /backup/rancher-data-backup--.tar.gz" ``` diff --git a/content/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/_index.md index e3be3ce786c..a9a9f1d1226 100644 --- a/content/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/_index.md +++ b/content/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/_index.md @@ -12,7 +12,7 @@ During upgrade, you'll enter a series of commands, filling placeholders with dat ``` -docker run --volumes-from rancher-data -v $PWD:/backup alpine tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher +docker run --volumes-from rancher-data -v $PWD:/backup busybox tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher ``` In this command, `-` is the version number and date of creation for a backup of Rancher. @@ -63,7 +63,7 @@ During upgrade, you create a copy of the data from your current Rancher containe ``` - docker run --volumes-from rancher-data -v $PWD:/backup alpine tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher + docker run --volumes-from rancher-data -v $PWD:/backup busybox tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher ``` **Step Result:** When you enter this command, a series of commands should run.