3 ms·

Docker swarm?

• skrebbel 7y ago
  Does anyone actually use it in anger though? I've not followed it well, but it seems to me like it's Docker Inc's failed attempt to compete with K8s, which doesn't bode well for its future.
  • jve 7y ago
    Anyway, it fills the gap between single node docker-compose and k8s. Because you can use docker-compose against swarm instance (so your app is running across multiple hosts) Swarm is so simple. Few commands and you can start scaling, routing, load balancing, desired state reconciliation https://docs.docker.com/compose/production/#running-compose-on-a-swarm-cluster https://docs.docker.com/compose/production/#running-compose-... Yeah, there is a concern about the docker swarm future: https://github.com/docker/swarm/issues/2965 https://github.com/docker/swarm/issues/2965 But mirantis just last week announced they will support and INVEST in docker swarm: https://www.mirantis.com/blog/mirantis-will-continue-to-support-and-develop-docker-swarm/ https://www.mirantis.com/blog/mirantis-will-continue-to-supp...
  • the_angry_angel 7y ago
    Yup. It’s good enough if you’re already invested in docker for dev and good enough if you’ve out grown a single machine. But not big enough for more than 10 nodes and user roles. From an ops point of view it’s simple to deploy and I’m yet to hit any really sharp edges. However the lack of cronjobs and init containers is an annoyance, but you can work around them. Mirantis’ recent announcement of further dev on Swarm after the initial announcement of only 2 years of support has not helped. I had been looking at moving to k8s. I’m now undecided if we should just continue with the plan to dump Swarm or keep it.