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

Merge pull request #1749 from skyscooby/patch-1

Browse Source 
Simplify and clarify placeholder example.
This commit is contained in:
Denise
2019-09-12 20:41:39 -07:00
committed by GitHub
parent a3076ff4a8 c6e62f0c00
commit 873c431063
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/upgrades/upgrades/single-node-upgrade/_index.md
+4 -3
View File
@@ -10,14 +10,15 @@ To upgrade Rancher Server 2.x when a new version is released, create a data cont
## Before You Start
During upgrade, you'll enter a series of commands, filling placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (`<EXAMPLE>`). Here's an example of a command with a placeholder:
During upgrade, you'll enter a series of commands, filling placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (`<EXAMPLE>`).
Here's an **example** of a command with a placeholder:
```
docker run --volumes-from rancher-data -v $PWD:/backup busybox tar zcvf /backup/rancher-data-backup-<RANCHER_VERSION>-<DATE>.tar.gz /var/lib/rancher
docker stop <RANCHER_CONTAINER_NAME>
```
In this command, `<RANCHER_VERSION>-<DATE>` is the version number and date of creation for a backup of Rancher.
In this command, `<RANCHER_CONTAINER_NAME>` is the name of your Rancher container.
Cross reference the image and reference table below to learn how to obtain this placeholder data. Write down or copy this information before starting the [procedure below](#completing-the-upgrade).