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

draft of single-node upgrade

Browse Source
This commit is contained in:
Mark Bishop
2018-05-15 17:05:19 -07:00
committed by Mark Bishop
parent ee8c1ec19a
commit ffcb82f1d6
3 changed files with 49 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/installation/ha-server-install/_index.md
+1 -1
View File
@@ -70,7 +70,7 @@ Before you install Rancher, confirm you meet the host requirements. Provision 3
>**Note:**
> The Load Balancer is in front of your Linux hosts. This can be any other host you have available, capable of running NGINX. Do not use one of your Rancher nodes to install the Load Balancer.
We will be using NGINX as our Layer 4 Load Balancer (TCP). NGINX will forward all connections to one of your Rancher nodes.
We will be using NGINX as our Layer 4 Load Balancer (TCP). NGINX will forward all connections to one of your Rancher nodes.
### Install NGINX
content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md
+5
View File
@@ -0,0 +1,5 @@
---
title: High Availability Upgrade
weight: 1020
draft: true
---
content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md
+43
View File
@@ -0,0 +1,43 @@
---
title: Single Node Upgrade
weight: 1010
draft: true
---
Upgrading Rancher Server running on a single node requires only a few commands.
1. Stop your Rancher container. Replace `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container.
```
docker stop <RANCHER_CONTAINER_ID>
```
>**Tip:** You can obtain the ID for your Rancher container by entering the following command: `docker container ls`
2. Create a `rancher-data` container. This container backs up the data from your current Rancher install, which you'll restore later.
```
docker create --volumes-from <RANCHER_CONTAINER_ID> \
--name rancher-data rancher/rancher:<RANCHER_CONTAINER_TAG>
```
3. Pull the most recent image of Rancher.
```
docker pull rancher/rancher:latest
```
4. Launch a new Rancher Server container using the `rancher-data` container.
```
docker run -d --volumes-from rancher-data --restart=unless-stopped \
-p 8080:8080 rancher/rancher:latest
```
>**Note:** _Do not_ stop the upgrade after initiating it, even if the upgrade process seems longer than expected. Stopping the upgrade may result in database migration errors during future upgrades.
><br/>
><br/>
>**Note:** After standing up your upgraded Rancher Server, data from your upgraded server is also saved to the `rancher-data` container for use in future upgrades.
5. Remove the previous Rancher Server container.
If you only stop the previous Rancher Server container (and don't remove it), the container may restart after the next server reboot.
**Result:** Rancher server is upgraded to the latest version.