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

moving rollbacks folder

Browse Source 
adjust links for folder move

Added troubleshooting of rke

Added clarification of rke version for troubleshooting

Update _index.md

moving rollbacks folder

moving rollbacks folder

moving rollbacks folder
This commit is contained in:
Mark Bishop
2018-08-01 15:49:48 -07:00
committed by Denise
parent e35291f71e
commit efb70142c1
5 changed files with 20 additions and 13 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
+38
View File
@@ -0,0 +1,38 @@
---
title: Rolling Back—Single Node Installs
weight: 25
aliases:
- /rancher/v2.x/en/backups/rollbacks/single-node-rollbacks
---
Rolling back an unsuccessful Rancher upgrade requires you to
restore the backup 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>
```
2. Stop the container currently running Rancher Server. Replace `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container.
```
docker stop <RANCHER_CONTAINER_ID>
```
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-<PRIOR_VERSION> \
-v $PWD:/backup alpine sh -c "rm /var/lib/rancher/* -rf \
&& tar zxvf /backup/<BACKUP_FILENAME>.tar.gz"
```
4. Start a new Rancher Server container with the `<PRIOR_VERSION>` tag pointing to the data container.
```
docker run -d --volumes-from rancher-data-<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.