Docker Swarm
docs.docker.com
- Free plan
- Windows
- Linux
- API
- Self-hosted
What Docker Swarm is
Docker Swarm is a cluster management mode built into Docker Engine for running production workloads across multiple Docker daemons. It is managed through the Docker CLI and does not require separate orchestration software. Managers use a declarative service model to maintain the requested state, including replica counts, networks, storage resources, and exposed ports. Services can be replicated or run globally, with one task on every node. Overlay networks connect daemons, and an ingress network supports load balancing. Services receive DNS names and can use virtual IP load balancing or DNS round-robin discovery. Swarm can roll out updates incrementally and revert to a previous service version. Nodes use mutual TLS for authentication and encrypted communications, with TLS 1.2 as the minimum. Application traffic on overlay networks is not encrypted by default; IPsec overlay encryption can impose a non-negligible performance penalty. Swarm is self-hosted, with no multi-cluster management or autoscaling. Docker recommends a maximum of seven manager nodes and /24 overlay network blocks, the latter limiting a network to 256 IP addresses. Nodes also need TCP/UDP port 7946 and, by default, UDP port 4789 for overlay traffic.
Who it suits
Docker Swarm may suit teams running production services across Docker daemons that want cluster management built into Docker Engine. It is self-hosted, so users need to plan for its network, manager, and overlay limits.
Good to know, and what to watch
- Built into Docker Engine and managed through the Docker CLI.
- Supports replicated and global services.
- Provides overlay networking and service discovery.
- Updates can roll out incrementally and roll back.
- Node communications use mutual TLS.
- Application traffic on overlays is not encrypted by default.
- IPsec overlay encryption can reduce performance.
- No multi-cluster management or autoscaling.
- Recommended /24 overlay blocks limit networks to 256 IP addresses.
Plans
Every plan and priceDocker Personal
Docker Swarm mode
Docker Pro
Docker Team
Open source
Getting started
- Install a current Docker Engine version
- Initialize or join nodes in a Swarm cluster
- Use the Docker CLI to define services
- Configure replicas, networks, storage, and exposed ports
- Deploy services and apply rolling updates as needed
Limits to check
Docker recommends a maximum of seven manager nodes, noting that more managers can reduce performance. Recommended /24 overlay networks limit each network to 256 IP addresses, and overlay application traffic is not encrypted by default.
The verdict
Swarm provides built-in cluster management, service discovery, and rolling updates for Docker workloads. Consider its self-hosted networking requirements, encryption defaults, and lack of autoscaling and multi-cluster management before adopting it.
Questions people ask
Does Docker Swarm cost anything?
Swarm mode is free and open source, and it is included in Docker Engine.
Is a free trial available?
No free trial is listed; Swarm mode itself is free.
What platforms are supported?
The listed platforms are API, Linux, self-hosted, and Windows.
Does Swarm support rolling updates?
Yes. Services can update incrementally and roll back to a previous version.
How are node communications secured?
Swarm nodes use mutual TLS for authentication and encrypted communication, with TLS 1.2 as the minimum.
Does it provide autoscaling or multi-cluster management?
No. The listed capabilities do not include autoscaling or multi-cluster management.
What the maker publishes
- Application traffic
- Application data over overlay networks is not encrypted by default; enabling overlay encryption with IPsec can impose a non-negligible performance penalty. source
- Built in
- Current Docker versions include Swarm mode in Docker Engine, managed through the Docker CLI, without additional orchestration software. source
- Manager limit
- Docker recommends a maximum of seven manager nodes and notes that adding managers can reduce performance. source
- Networking
- Swarm supports overlay networks for communication among Docker daemons in the cluster and includes an ingress network for load balancing. source
- Network requirements
- Swarm nodes need TCP/UDP port 7946 for network discovery and UDP port 4789 by default for overlay data traffic. source
- Overlay limit
- Docker recommends /24 overlay network blocks, which limit a network to 256 IP addresses. source
- Purpose
- Swarm mode is an advanced feature for managing a cluster of Docker daemons and is intended for production runtime environments. source
- Scheduling
- Swarm supports replicated services and global services that run one task on every node. source
- Security
- Swarm nodes use mutual TLS to authenticate and encrypt communications, with a minimum TLS version of 1.2. source
- Service discovery
- Swarm assigns services DNS names and supports virtual IP load balancing or DNS round-robin discovery. source
- Service model
- Services use a declarative model in which managers work to maintain the desired state, including replica count, networks, storage resources, and exposed ports. source
- Updates
- Swarm can roll out service updates incrementally and roll back to a previous service version if something goes wrong. source
Checked against the maker's pages on 7 Oct 2026.