mirror of
https://github.com/docker/docs.git
synced 2026-04-04 10:18:57 +07:00
e44f5d8796
- Close #194 and fix - Fix and close #425 - Fix and close #417 - Fix and close #420 - Fix and close #422 - Adding in documentation build scripts - Fix and close #431 - Fix and close #438, and Fix and close #429 - Work on 441 - Adding in commands reference - Updating all the options to tables - Updating per Vivek #498 - Adding vivek's last suggestions Signed-off-by: Mary Anthony <mary@docker.com>
1.5 KiB
1.5 KiB
+++ title = "upgrade" description = "Upgrade UCP controller" [menu.main] identifier = "ucp_upgrade" parent = "ucp_ref" +++
upgrade
docker run --rm -it \
--name ucp \
-v /var/run/docker.sock:/var/run/docker.sock \
docker/ucp \
upgrade [OPTIONS]
Description
Upgrades UCP on a node. When upgrading UCP, you must run the upgrade command
against every server and node running Docker Engine in your cluster. You should
upgrade your controller and replica nodes first, followed by your compute nodes.
Depending on the upgrade path for your version of UCP, you may also need to
upgrade Docker Engine. You can also choose to upgrade Docker Engine simply
because a new version is available. Always upgrade a node`s Docker Engine
installation before upgrading its UCP installation.
After upgrading each node, confirm the node is present in the UCP console before proceeding to the next node.
Options
| Option | Description |
|---|---|
--debug, -D |
Enable debug. |
--jsonlog |
Produce json formatted output for easier parsing. |
--interactive, -i |
Enable interactive mode.,You will be prompted to enter all required information. |
--image-version "latest" |
Select a specific UCP version. |
--id |
The ID of the UCP instance to upgrade. |
--pull "always" |
Specify image pull behavior (always, when missing, or never). |