swarmkit

Eh, it's not quite that simple. What the person above you is thinking of is almost certainly "swarm classic" which is actually dead (see: https://github.com/docker-archive/classicswarm) Docker does support a different "Swarm mode" style deployment configuration, which is functionally https://github.com/moby/swarmkit, and really feels much more like Kubernetes to me than the original docker swarm. I'm... honestly not sure why you'd pick it as a solution over all the k8s tooling they've been doing instead. It feels like the same level of complexity and then only benefit is that it's easier to configure than bare metal k8s, but things like k3s and microk8s tackle that same space. If anyone is really using the swarm mode for a production service, I'd love to hear different opinions, though!

I thought docker-swarm had been considered neglected to the point of dead and without a future for a few years now. Is this impression incorrect/outdated? EDIT: So apparently what used to be known as "Docker Swarm" has been posthumously renamed to "Swarm Classic"/"Classic Swarm" and is indeed dead, abandoned, and deprecated. The project currently known as "Docker Swarm" is a younger completely different project which appears actively maintained. "Classic" still has roughly twice the GH stars and forks compared to the new one. I can't be the only one who's dismissed the latter, assuming it to be the former. Very confusing naming and branding, they would probably have more way more users if they had not repurposed the name like this. https://github.com/docker-archive/classicswarm > Swarm Classic: a container clustering system. Not to be con

This doesn't look that abandoned? https://github.com/moby/swarmkit Or are you talking about swarm the product (versus docker swarm mode)

Docker Swarm is getting some more attention after having been neglected, with repo activity going up[1], and Mirantis even publishing a sponsored article on The Next Web[2]. Things look brighter for Swarm than one year ago. Interest in Docker Swarm also persist I think. My post on starting Docker Swarm in 2022 [3] on my very low profile blog gets very regular visits. [1]: https://github.com/moby/swarmkit/commits/master [2]: https://thenewstack.io/docker-swarm-a-user-friendly-alternat... [3]: https://www.yvesdennels.com/posts/docker-swarm-in-2022/

Swarm is (and always has been) an independent project: github.com/docker/swarmkit

Swarm was interesting, but it seems that both SwarmKit and "Classic Swarm" are dead[1][2], with no real activity since 2018. Kubernetes, for better or for worse, has clearly completely won. Not that this article isn't interesting for it's own sake, but it's just something to consider. 1. https://github.com/docker/swarmkit/graphs/contributors 2. https://github.com/docker/classicswarm/graphs/contributors

Swarm was interesting, but it seems that both SwarmKit and "Classic Swarm" are dead[1][2], with no real activity since 2018. Kubernetes, for better or for worse, has clearly completely won. Not that this article isn't interesting for it's own sake, but it's just something to consider. 1. https://github.com/docker/swarmkit/graphs/contributors 2. https://github.com/docker/classicswarm/graphs/contributors

Swarm was interesting, but it seems that both SwarmKit and "Classic Swarm" are dead[1][2], with no real activity since 2018. Kubernetes, for better or for worse, has clearly completely won. Not that this article isn't interesting for it's own sake, but it's just something to consider. 1. https://github.com/docker/swarmkit/graphs/contributors 2. https://github.com/docker/classicswarm/graphs/contributors

Is that swarm in general, or v1 swarm that predated the current "swarmkit"? https://forums.docker.com/t/is-there-a-roadmap-for-docker-sw... https://github.com/docker/swarmkit/issues/2665

I wrote the initial implementation of the raft subsystem and it was definitely not a copy/paste. We started from scratch (using etcd's core raft) with the transport layer being grpc. My initial experiment could be found in this repository [1]. I then took the code from my initial experiment and included this into Swarmkit [2]. From there we went through many iterations on the initial code base and improved the UI with Docker swarm `init`/`join`/`leave` to make the experience of managing the cluster "friendly". We spent quite some time evaluating different raft and paxos implementations (mostly Consul and etcd raft libraries), and found out etcd to be the most stable and flexible for our use case. It was very easy for example to swap the transport layer to use grpc. The fact that etcd implementation is represented as a simple state machine

Docker staff have been saying words to the effect of "we'll make an announcement with info soon!" for at least the last three+ months, across several projects. Swarm, Docker-Machine, & Infrakit come to mind. With no actual announcement(s) then occurring. The commit activity graph on InfraKit - which people are supposed to use now that Docker-Machine has been deprecated - seems pretty clear: https://github.com/docker/infrakit/graphs/contributors SwarmKit is the same: https://github.com/docker/swarmkit/graphs/contributors Clearly these aren't where resources have been placed. Actions are not lining up with the words given. :(

Check this GitHub issue on SwarmKit for more info: https://github.com/docker/swarmkit/issues/2665

Yep I wrote this, and it needs an update just months later. Lots happening. Even today a big PR was pulled in to improve the scalability of Swarm https://github.com/moby/moby/pull/37372 More updates here https://github.com/docker/swarmkit/issues/2665#issuecomment-...

Could it be that the teams are simply focused on adding K8s support and getting the Docker EE out of Beta? Public statement on their blog after the K8s announcement in EU: "But it’s equally important for us to note that Swarm orchestration is not going away. Swarm forms an integral cluster management component of the Docker EE platform; in addition, Swarm will operate side-by-side with Kubernetes in a Docker EE cluster, allowing customers to select, based on their needs, the most suitable orchestration tool at application deployment time." https://blog.docker.com/2017/11/swarm-orchestration-in-docke... There's still plenty of PR's and activity in the SwarmKit and Libnetwork repos: https://github.com/docker/swarmkit/pulse/monthly https://github.com/docker/libnetwork/pulse/monthly

You may be looking for swarmkit https://github.com/docker/swarmkit