Docker Swarm
Manage a Docker Swarm cluster, services, stacks, configs, secrets, and node agents.
Use Docker Swarm instead of Compose projects when an app should run on several hosts or survive a host going down. Swarm is Docker’s built-in clustering mode: hosts join one cluster, and Swarm schedules, replicates, and restarts services across them.
Get started
Section titled “Get started”- Connect each host as a Remote Agent.
- Open Swarm → Cluster to see each agent’s Swarm role. Initialize a Swarm on one if needed.
- Add hosts with Easy Join from a manager’s row on the Cluster page, or an agent’s detail page or row menu. Arcane fills in the manager address and join token.
- Create the app’s Configs and Secrets.
- Deploy from Stacks.
- Check rollout health and logs under Services and Tasks.
Swarm pages cover every agent you can read, and each action runs on the agent of the row you act on.
What’s in the workspace
Section titled “What’s in the workspace”| Page | What it covers |
|---|---|
| Cluster | Initialize a Swarm, join, leave, unlock, rotate join tokens, update cluster spec. |
| Workloads | Stacks, services, tasks, scaling, rollbacks, logs. |
| Nodes & Agents | Node operations, agent coverage, deployment, and fixing agent links. |
| Configs & Secrets | Create and delete configs and secrets, and when to use each. |
Where the data comes from
Section titled “Where the data comes from”Arcane reads cluster resources from Swarm manager agents. If several of yours manage one cluster, Arcane reads through one, so each resource is listed once; the Agent column shows which manager. Stacks are grouped by the com.docker.stack.namespace service label, so stacks created outside Arcane show up too. Agents on nodes add access to each node’s containers and images; services and stacks stay visible without them (see Nodes & Agents).
Permissions and modes
Section titled “Permissions and modes”- Swarm lists include only manager agents; workers appear on the Cluster page. Cluster actions such as unlock, token rotation, and spec updates need a Swarm manager agent.
- Viewing Swarm resources needs
swarm:read. Each change needs its own permission, such asswarm:init,swarm:join,swarm:unlock,swarm-nodes:update,swarm-services:create, orswarm-stacks:create. See the permission catalog.