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

Updating per feedback

Browse Source
This commit is contained in:
Jennifer Travinski
2022-07-11 14:07:53 -04:00
parent 49bd1b90c5
commit cbf9566431
14 changed files with 16 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/installation/other-installation-methods/single-node-docker/single-node-rollbacks/single-node-rollbacks.md
+1 -1
View File
@@ -82,7 +82,7 @@ Rolling back to a previous version of Rancher destroys any changes made to Ranch
```
Privileged access is [required.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher)
:::note Important:
:::danger
**_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.
docs/en/installation/other-installation-methods/single-node-docker/single-node-upgrades/single-node-upgrades.md
+2 -2
View File
@@ -5,7 +5,7 @@ weight: 1010
The following instructions will guide you through upgrading a Rancher server that was installed with Docker.
:::note Important:
:::caution
**Docker installs are not supported in production environments.** These instructions are provided for testing and development purposes only. If you have already deployed a Docker install in production and need to upgrade to a new Rancher version, we recommend [migrating to the Helm chart install]({{<baseurl>}}/rancher/v2.6/en/backups/migrating-rancher/) before upgrading.
@@ -116,7 +116,7 @@ docker pull rancher/rancher:<RANCHER_VERSION_TAG>
Start a new Rancher server container using the data from the `rancher-data` container. Remember to pass in all the environment variables that you had used when you started the original container.
:::note Important:
:::danger
**_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.