From 22d742661754c01a361597fecc89dc46e004a407 Mon Sep 17 00:00:00 2001 From: Denise Schannon Date: Thu, 23 Aug 2018 12:25:33 -0700 Subject: [PATCH] fixing rollback docs --- .../en/upgrades/rollbacks/single-node-rollbacks/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 a7f6e85e8ab..08bac2e9107 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 @@ -26,14 +26,14 @@ docker stop 3. Go to the location where you saved your [backup tar balls]({{< baseurl>}}/rancher/v2.x/en/upgrades/single-node-upgrade/#backup). Run the following command to create a data container from the backup tar ball. ``` -docker run --volumes-from rancher-data- \ +docker run --volumes-from rancher-data \ -v $PWD:/backup alpine sh -c "rm /var/lib/rancher/* -rf \ && tar zxvf /backup/.tar.gz" ``` 4. Start a new Rancher Server container with the `` tag pointing to the data container. ``` -docker run -d --volumes-from rancher-data- \ +docker run -d --volumes-from rancher-data \ --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher: ``` >**Note:** _Do not_ stop the rollback after initiating it, even if the rollback process seems longer than expected. Stopping the rollback may result in database issues during future upgrades.