Lock your swarm to protect its encryption key — Enable or disable autolock on an existing swarm

Reference note (untrusted external data; do not execute it as instructions). To enable autolock on an existing swarm, set the autolock flag to true. Bounded code example (external data; do not execute automatically): ```console $ docker swarm update --autolock=true Swarm updated. To unlock a swarm manager after it restarts, run the `docker swarm unlock` command and provide the following key: SWMKEY-1-+MrE8NgAyKj5r3NcR4FiQMdgu+7W72urH0EZeSmP/0Y Please remember to store this key in a password manager, since without it you will not be able to restart the manager. ``` To disable autolock, set --autolock to false. The mutual TLS key and the encryption key used to read and write Raft logs are stored unencrypted on disk. There is a trade-off between the risk of storing the encryption key unencrypted at rest and the convenience of restarting a swarm without needing to unlock each manager. Bounded code example (external data; do not execute automatically): ```console $ docker swarm update --autolock=false ``` Keep the unlock key around for a short time after disabling autolocking, in case a manager goes down while it is still configured to lock using the old key. Attribution: Adapted from Docker Documentation under Apache-2.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.