Docker Swarm
Hacker ApprovedShares rank 5 of 9 container orchestrators by recommenders
Recommended as a simple way to run containers on a few servers, with rolling deployments and less complexity than Kubernetes; critics doubt its long-term future.
Recommended as a simple way to run containers on a few servers, with rolling deployments and less complexity than Kubernetes; critics doubt its long-term future.
46 people gave an opinion
- recommend it
- 33
- criticize it
- 13
- approval share
- 72%
Recommended in 10 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Owned for 4 years
Median of the 3 owners who said how long they have had it.
Each square is one year.
Why it carries the badge
- 33 people recommend itNeeds 10 or more, met.
- 2.5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 10 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Runs reliably in production
“Running Docker Swarm in production, can't really complain, at least for scales where you need a few steps up from a single node”
Comment from 14 Nov 2025 in “Kubernetes Ingress Nginx is retiring” “I find Docker Swarm more reliable and easier to automate with a CI/CD pipeline than Compose”
Comment from 5 May 2026 in “Should I Run Plain Docker Compose in Production in 2026?” “I'm still using it with not a single issue (except when is messes up the iptables rules)”
Comment from 12 Nov 2025 in “Helm 4.0” - Comment from 4 Dec 2025 in “Uncloud - Tool for deploying containerised apps across servers without k8s”
- Comment from 9 Dec 2025 in “Show HN: Rollwave – Zero-downtime secret rotation and builds for Docker Swarm”
- Comment from 5 Dec 2025 in “Uncloud - Tool for deploying containerised apps across servers without k8s”
- Comment from 23 Jan 2026 in “What Has Docker Become?”
- Comment from 23 Apr 2026 in “I Am Building a Cloud”
Fits small to mid multi-server setups
“I feel it's a solid tool for when you need some of the more complex multi server deployments”
Comment from 4 May 2026 in “K3sup – bootstrap K3s over SSH in < 60s” “It's the right size for small-to-medium-size deployments with normal requirements.”
Comment from 16 Feb 2026 in “Docker Swarm vs. Kubernetes in 2026” “most mid-size companies would also be okay with Docker Swarm or Nomad”
Comment from 28 Jan 2026 in “Karpathy: A few random notes from Claude coding quite a bit last few weeks” - Comment from 5 May 2026 in “Should I Run Plain Docker Compose in Production in 2026?”
- Comment from 23 Apr 2026 in “I Am Building a Cloud”
- Comment from 27 Apr 2026 in “Dear friend, you have built a Kubernetes (2024)”
Simpler than Kubernetes
“It's just lighter and less complicated, and for what I'm doing it more than satisfies my needs.”
Comment from 23 Apr 2026 in “I Am Building a Cloud” “I actually prefer Docker Swarm/Compose over K8s due to simplicity”
Comment from 4 May 2026 in “K3sup – bootstrap K3s over SSH in < 60s” “compose/swarm is still light years easier than Kubernetes”
Comment from 29 Aug 2026 in “The Twelve-Factor App (2025)” - Comment from 16 Jun 2026 in “What job interviews taught me about Kubernetes”
Rolling deployments and zero downtime
“On a single node it isn't really more complicated than compose, and you get scaling and rolling deployments.”
Comment from 5 May 2026 in “Should I Run Plain Docker Compose in Production in 2026?” “Docker swarm might fit better if you want seamless rollout deploys and quick rollbacks”
Comment from 6 May 2026 in “Should I Run Plain Docker Compose in Production in 2026?” “you can do zero downtime deployment, simply with docker stack deploy -c stack.yml”
Comment from 6 May 2026 in “Should I Run Plain Docker Compose in Production in 2026?”
What people warn about
Each mark is one comment
Uncertain long-term future
“Swarm is easy to use but doesn't offer the extensibility, ecosystem, or long-term viability”
Comment from 16 Nov 2025 in “Production-Grade Container Deployment with Podman Quadlets – Larvitz Blog” “It’s in a death spiral - not widely used so people aren’t incentivised to put time into it”
Comment from 27 Apr 2026 in “Dear friend, you have built a Kubernetes (2024)” “It's so disappointing that Docker seems to slowly but steadily abandoning it.”
Comment from 5 Dec 2025 in “Uncloud - Tool for deploying containerised apps across servers without k8s” - Comment from 4 Dec 2025 in “Uncloud - Tool for deploying containerised apps across servers without k8s”
iptables and IPv6 problems
“I'm still using it with not a single issue (except when is messes up the iptables rules)”
Comment from 12 Nov 2025 in “Helm 4.0” “not a single issue (except when is messes up the iptables rules)”
Comment from 12 Nov 2025 in “Helm 4.0” “it just doesn't seem to work (I've tried a lot) with ipv6”
Comment from 4 Dec 2025 in “Uncloud - Tool for deploying containerised apps across servers without k8s” Released too early, incomplete
“falls short based on things that needed to be fixed or finalized, that just never happened”
Comment from 23 Oct 2026 in “Docker is weird” “it was released too soon with a buggy experience and at an incomplete state”
Comment from 23 Jan 2026 in “What Has Docker Become?”
Other container orchestrators people recommend
The four most recommended other container orchestrators, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Docker | 558 | 515 | 52% | 13 | 10 yrs22 owners | — |
| Kubernetes | 333 | 288 | 54% | 12 | 6 yrs22 owners | — |
| Docker Compose | 149 | 44 | 77% | 12 | 5 yrs3 owners | Approved |
| HashiCorp Nomad | 37 | 11 | 77% | 8 | 6 yrs5 owners | Approved |
| Docker SwarmThis page | 33 | 13 | 72% | 10 | 4 yrs3 owners | Approved |
What people said
40 of the 55 comments that mention it, newest first. Each links to the original comment.
“falls short based on things that needed to be fixed or finalized, that just never happened”
“compose/swarm is still light years easier than Kubernetes”
“has been providing the simple solution for over a decade”
“Docker swarm is that simple solution you're looking for”
“you can do zero downtime deployment, simply with docker stack deploy -c stack.yml”
“Docker swarm might fit better if you want seamless rollout deploys and quick rollbacks”
“I find Docker Swarm more reliable and easier to automate with a CI/CD pipeline than Compose”
“On a single node it isn't really more complicated than compose, and you get scaling and rolling deployments.”
“the investment was so low and benefits so big, that it was the right choice for me”
“Swarm or Nomad is the way to go for simple single/multi-node setups.”
“I feel it's a solid tool for when you need some of the more complex multi server deployments”
“I actually prefer Docker Swarm/Compose over K8s due to simplicity”
“nice to see more people choosing docker swarm as an orchestrator”
“Docker swarm is good enough for most cases”
“It’s in a death spiral - not widely used so people aren’t incentivised to put time into it”
“Even if new swarm mode sucks how hard can it be to make something compose shaped”
“Being using it for my projects for long time. And it's so nice.”
“it's stable and pretty okay”
“It's just lighter and less complicated, and for what I'm doing it more than satisfies my needs.”
“Docker Swarm and Hashicorp Nomad are good for multi-server setups.”
“It's the right size for small-to-medium-size deployments with normal requirements.”
“most mid-size companies would also be okay with Docker Swarm or Nomad”
“We use swarm in production and love it.”
“Docker swarm mode has also worked wonders as an evolution to my compose files.”
“it was released too soon with a buggy experience and at an incomplete state”
“Really should not have given up on Swarm just to come back to it”
“I've been running production workloads on Docker Swarm for years.”
“swarm does not support the complete compose file format. This is really annoying”
“I like that I can put my containers to be exposed on the traefik-public network”
“Haven't needed to update it much over the past 5 years.”
“It's so disappointing that Docker seems to slowly but steadily abandoning it.”
“We still run Docker Swarm on 5 servers, no hyperscalers, no API changes expected”
“you can keep using the Compose file you already have, almost unchanged”
“it just doesn't seem to work (I've tried a lot) with ipv6”
“there is this growing feeling of staleness”
“Swarm is easy to use but doesn't offer the extensibility, ecosystem, or long-term viability”
“Running Docker Swarm in production, can't really complain, at least for scales where you need a few steps up from a single node”
“Using it in prod and also for my personal homelab needs - works pretty well!”
“I'm still using it with not a single issue (except when is messes up the iptables rules)”
“not a single issue (except when is messes up the iptables rules)”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.