[justinclift]

> I still don't quite understand why Docker Swarm is so overlooked.

No IPv6 support in it at all, and the company seems to have moved resources internally away from Swarm development.

Doesn't bode well for it's future. Expecting it'll be taken out to the back shed (-bang-) in a while.

[ofrzeta]

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

[justinclift]

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. :(

[ofrzeta]

I guess you are right. It's unfortunate because judging from the comments here you would think that there's a market for a simpler orchestration software while it will be hard to compete as just another Kubernetes distributor (even more so now that there are several alternatives for the container runtime). But hey, what do I know about product management?! :)

[josegonzalez]

Nomad is that. We run Nomad quite successfully at SeatGeek, and I know of several Very Large Companies™ doing so at scale as well. One of them even has a fruit logo.

[ofrzeta]

You are using the enterprise version, I assume?

[josegonzalez]

We are running the OSS version of Consul, Nomad, and Vault. While the enterprise versions provide some items that could be interesting, they are not necessary given our workflow, and I'd bet that the majority of development shops out there wouldn't need them either (though I am certainly more than happy to play with them!).