docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Review upgrade docs for 2.0

This commit is contained in:
Joao Fernandes 2016-09-30 17:33:49 -07:00
parent 90e7e82e47
commit 99383268ca
1 changed files with 13 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
installation/upgrade-major.md
View File

@ -23,16 +23,15 @@ other relevant information for upgrading to a particular version.
## Plan the upgrade ## Plan the upgrade
As part of the upgrade process, you'll be upgrading the CS Docker Engine As part of the upgrade process, you'll be upgrading the CS Docker Engine
installed in each node of the cluster. When this happens, all containers installed in each node of the cluster to version 1.12. If you're currently
running on that node will be stopped, causing some downtime to the cluster running CS Docker Engine 1.11.2-cs3, all containers will be stopped during the
management functionality and your applications. upgrade, causing some downtime to UCP and your applications.
You should plan for the upgrade to take place outside business hours, to ensure You should plan for the upgrade to take place outside business hours, to ensure
there's minimal impact to your users. there's minimal impact to your users.
Also, don't make changes to the cluster configurations while you're upgrading Also, don't make changes to UCP configurations while you're upgrading it. That
the cluster. That can lead to misconfigurations that are difficult to can lead to misconfigurations that are difficult to troubleshoot.
troubleshoot.
## Backup your cluster ## Backup your cluster
@ -55,7 +54,11 @@ Starting with the controller nodes, and then worker nodes:
[Follow the upgrade procedure](/cs-engine/upgrade.md) to upgrade the [Follow the upgrade procedure](/cs-engine/upgrade.md) to upgrade the
CS Docker Engine. This will cause some downtime on that node, since all CS Docker Engine. This will cause some downtime on that node, since all
containers running there will be restarted. containers will be stopped.
Containers that have a restart policy set to
'always', are automatically started after the upgrade. This is the case of
UCP and DTR components. All other containers need to be started manually.
3. Make sure the node is healthy. 3. Make sure the node is healthy.
@ -72,7 +75,8 @@ that you've installed using that node's root CA material.
2. Pull the docker/ucp image for the version you want to upgrade to. 2. Pull the docker/ucp image for the version you want to upgrade to.
```bash ```bash
$ docker pull docker/ucp:2.0.0 # Check on Docker Hub which versions are available
$ docker pull docker/ucp:<version>
``` ```
3. Upgrade UCP by running: 3. Upgrade UCP by running:
@ -81,7 +85,7 @@ that you've installed using that node's root CA material.
$ docker run --rm -it \ $ docker run --rm -it \
--name ucp \ --name ucp \
-v /var/run/docker.sock:/var/run/docker.sock \ -v /var/run/docker.sock:/var/run/docker.sock \
docker/ucp:2.0.0 \ docker/ucp:<version> \
upgrade --interactive upgrade --interactive
``` ```