moby / moby/swarmkit

Where are swarm releases ?

Open
#3,175 2 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
3.7k
Forks
676
Avg merge
4d 9h
Merged PRs (30d)
6

Description

Hello,

We try to determine if using docker swarm in production (for us or our clients) is a viable solution on along term basis.

I mean actually we are deploying our apps with docker-compose or kubernetes but we lack a simple multi-node deployment between these solutions.
Using docker swarm seems the obvious solution to jump from a mono machine deployment with docker compose to something very close but just with the multi machine feature.

The problem is that it is very difficult to find if swarm is a living project or not, because it relies on the docker-compose and moby/moby projects, which have a lot of activity, but the swarm project itself show only a few tags and no releases:

So if we try to estimate the liveliness with the release frequency swarm seems dead.
It is sad as it may not be the case and the project itself is a beautiful one.

Is there something wrong when I try to estimate the activity of the swarm project just by looking at the releases in github ?
Should I look somewhere else to justify to my manager going to swarm for production is credible ?

Related (old) discussion here

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the swarmkit tags and releases pages linked in the issue, then read the related discussion in issue 2665. Determine where project activity and release guidance are currently documented, and provide a clear source that addresses whether release frequency accurately reflects Swarm's maintenance status and production viability.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
devops, infrastructure, release
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.