53442a4788
edited screen snap breaking out topics for Docker Cloud swarm mode added another where-to-next link added more where-to-next links added back in on-page TOC for create swarm topic incorporated Ryan's review comments on first draft more Ryan's review comments, sweep thru all for consistency, notoc on short pages, etc. removed duplicate link to 'create a new swarm in docker cloud' Laura's comments incorporated re-organized Cloud topics, added in Swarm Mode Ryan's review comments on Cloud, added new type of advisory for Beta previews more review comments, manage infrastructure --> standard mode fixing image testing cloud images updates to Cloud welcome page for Swarm, non-Swarm descriptions add new cloud repository image retake of corrupted image fixed the other instance of corrupted image by referencing the retake fixing corrupted image on GitHub Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
1.5 KiB
description, keywords, redirect_from, title
| description | keywords | redirect_from | title | ||
|---|---|---|---|---|---|
| Upgrade Docker Engine on a node | upgrade, engine, node |
|
Upgrade Docker Engine on a node |
Docker Cloud helps you manage nodes that have Docker Engine installed on them. You can upgrade the version of Docker Engine on your nodes when new versions are released. Docker Cloud doesn't automatically upgrade your nodes for you because your containers would need to be restarted to complete the upgrade. Instead, we allow you to choose when you want to upgrade so you can plan for potential outage time during the restart.
Upgrading Docker Engine in a node
Before you upgrade your nodes,
Go to the detail page of the node that you want to upgrade. On the left side you will see a Docker Info section that lists the currently installed version of Docker Engine.
If a new version is available, you'll see an up-arrow icon, and a New Docker version available message above the current version line. Click the up-arrow icon to start the upgrade process.
After upgrading Docker Engine, any containers that was running before the upgrade is automatically restarted, regardless of the autorestart setting. Containers that were stopped are not restarted.
Upgrading nodes using the API and CLI
See our API and CLI documentation for more information on how to upgrade nodes with our API, SDKs and the CLI.