docker/ucp restoreEstimated reading time: 2 minutes
Restore a UCP cluster from a backup.
docker container run --rm -i \ --name ucp \ -v /var/run/docker.sock:/var/run/docker.sock \ docker/ucp \ restore [command options] < backup.tar
This command installs a new UCP cluster that is populated with the state of
a previous UCP manager node using a tar file generated by the
All UCP settings, users, teams and permissions will be restored from the backup
file. The Restore operation does not alter or recover any containers, networks,
volumes or services of an underlying cluster.
The restore command can be performed on any manager node of an existing
cluster. If the current node does not belong in a cluster, one will be
initialized using the value of the
--host-address flag. When restoring on an
existing swarm-mode cluster, no previous UCP components must be running on any
node of the cluster. This cleanup can be performed with the
If restore is performed on a different cluster than the one where the backup file was taken on, the Cluster Root CA of the old UCP installation will not be restored. This will invalidate any previously issued Admin Client Bundles and all administrator will be required to download new client bundles after the operation is completed. Any existing Client Bundles for non-admin users will still be fully operational.
By default, the backup tar file is read from stdin. You can also bind-mount the
backup file under
/config/backup.tar, and run the restore command with the
uninstall-ucpbefore attempting the restore operation on an existing UCP cluster.
If your swarm-mode cluster has lost quorum and the original set of managers are not recoverable, you can attempt to recover a single-manager cluster with
docker swarm init --force-new-cluster.
You can restore from a backup that was taken on a different manager node or a different cluster altogether.
||Enable debug mode|
||Produce json formatted output for easier parsing|
||Run in interactive mode and prompt for configuration values|
||Address or interface to use for data path traffic|
||Force the install/upgrade even if the system does not meet the minimum requirements|
||The network address to advertise to other nodes. Format: IP address or network interface name|
||Decrypt the backup tar file with the provided passphrase|
||Add subject alternative names to certificates (e.g. --san www1.acme.com --san www2.acme.com)|
|`--swarm-grpc-port value||Port for communication between nodes (default: 2377)|
||The unlock key for this swarm-mode cluster, if one exists.|