public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-24 20:18:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revert "clarifying what data container to use for rollbacks"

Browse Source 
This reverts commit 7fbe122647963a369f2246401f34b4806956444e.
This commit is contained in:
Mark Bishop
2018-08-28 14:44:38 -07:00
committed by Denise Schannon
parent 0c54f49ae5
commit f389cce861
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/_index.md
+2 -2
View File
@@ -31,9 +31,9 @@ docker run --volumes-from rancher-data \
&& tar zxvf /backup/<BACKUP_FILENAME>.tar.gz"
```
4. Start a new Rancher Server container that uses the `<RANCHER_VERSION>` data container that you created in [Step 3]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/#backup) of [Single Node Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade).
4. Start a new Rancher Server container with the `<PRIOR_VERSION>` tag pointing to the data container.
```
docker run -d --volumes-from rancher-data \
--restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher:<RANCHER_VERSION>
--restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher:<PRIOR_VERSION>
```
>**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.