From b9945c10cd2c3a91b7bab4ce1896f7be1bbfcf58 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Mon, 25 Jun 2018 12:14:58 -0700 Subject: [PATCH] new container --- .../v2.x/en/upgrades/single-node-upgrade/_index.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md index 35a3b5b00fa..5e18b63f9df 100644 --- a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md +++ b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md @@ -27,6 +27,16 @@ docker create --volumes-from \ --name rancher-data rancher/rancher: ``` +1. Create a different `rancher-data-snapshot` container. This container also backs up the data from your current Rancher Server, but you are creating this container to serve as a restoration point in case something goes wrong with your server upgrade. + + - Replace `` with the same ID from the previous step. + - Replace `` with the version of Rancher that you are currently running, as mentioned in the **Prerequisite** above. + + ``` +docker create --volumes-from \ +--name rancher-data rancher/rancher: + ``` + 3. Pull the most recent image of Rancher. ```