Start a swarm, join one, and keep the keys.
On a daemon that is not a manager: create a swarm, join one, unlock a locked manager, or leave. On a manager: the join tokens, autolock with the unlock key, the heartbeat, the task history and the certificates. And a way back when the swarm has lost its quorum.
What you can do
Create a swarm
On a daemon that is not a manager, create a swarm, with suggestions for its address.
Join one
Pick a manager that is also a Docker context in the app, and the app fetches the token and the address there; a manager inside Docker Desktop is refused, as other machines cannot reach its address. Or paste the whole join command, and recover from a join that failed.
Unlock
A manager of a swarm with autolock needs the unlock key after a restart; the app unlocks it.
Leave
A manager demotes itself before it leaves, so the swarm keeps its quorum; the last manager has to type its name.
Join tokens
Show and copy the tokens for workers and managers, copy the docker swarm join command, or renew a token.
Autolock
Turn on autolock, and keep the unlock key that managers need after a restart.
Heartbeat and history
How often nodes report to the managers, and how many old tasks are kept per replica.
Certificates
How long a node certificate is valid (each node renews its own), until when the root certificate of the swarm's CA is valid, and rotating the CA (docker swarm ca --rotate), with how many nodes already have a certificate from the new one.
Recover the quorum
When too few managers are reachable, the swarm has no leader and the overview says so. Recover lists the managers, which of them still answer through a Docker context, and lets one of them start a new cluster as the only manager with all services, networks, secrets and configs (docker swarm init --force-new-cluster). You type the name of that node first: it cannot be undone.
The Hyper-V firewall
When the engine runs in WSL with mirrored networking, the app checks whether the Hyper-V firewall lets the swarm ports through, and the ports of a service or of a stack you are about to deploy. For what is missing it gives the New-NetFirewallHyperVRule commands to run in PowerShell as administrator, limited to your own network; it does not change the firewall itself.
All features