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

restructuring for site updates

Browse Source
This commit is contained in:
Mark Bishop
2018-06-26 13:25:27 -07:00
committed by Mark Bishop
parent 28ff80ee65
commit f5417942e2
16 changed files with 56 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/backups/rollbacks/single-node-rollbacks/_index.md
+27
View File
@@ -0,0 +1,27 @@
---
title: Rolling Back—Single Node Installs
weight: 25
---
Rolling back an unsuccessful Rancher upgrade requires you to run the upgrade command again, with a couple of modifications:
- Run the upgrade command using the server tag for your prior Rancher install.
- Run the upgrade command while pointing toward the backup container you created while completing [Single Node Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrade-scenarios/single-node-upgrade/).
>**Warning!** Rolling back to a previous version of Rancher destroys any changes made to Rancher following the upgrade. Unrecoverable data loss may occur.
1. Pull the version of Rancher that you were running prior to upgrade.
```
docker pull rancher/rancher:<PRIOR_VERSION>
```
1. Launch a Rancher Server container that you created while completing [Step 3 of Single Node Upgrade]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrade-scenarios/single-node-upgrade/#backup).
Replace the `<PRIOR_VERSION>` placeholders with the version number of Rancher that you're rolling back to before upgrade.
```
docker run -d --volumes-from rancher-data-snapshot-<PRIOR_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.