When comparing Rancher vs Docker Swarm, the Slant community recommends Docker Swarm for most people. In the question“What are the best Docker orchestration tools?” Docker Swarm is ranked 2nd while Rancher is ranked 5th. The most important reason people chose Docker Swarm is:
This also means that containers can be launched with a simple `docker run` command and Swarm will take care of the rest, such as selecting the appropriate host on which to run the container.
Ranked in these QuestionsQuestion Ranking
Pro Web GUI cluster management
Intuitive and easy to use web gui.
Pro Mult-environment cluster system
- Cattle (Rancher default)
Pro Service catalog is easy
Rancher provides a catalog of application templates that make it easy to deploy complex stacks.
- Rancher certified catalog
- Community service catalog
Pro Self-service application stack for self-monitoring
Great contributions from the co community who build the service stack catalog.
One of them is the "Prometheus" template which deploys a collection of containers for monitoring a platform. It's capable of querying all aspects of your environment with some nice pre-built dashboards.
Pro Access control polices
Detailed role-based access control policies can be defined independently for each cluster.
Pro Easy setup
This also means that containers can be launched with a simple
docker run command and Swarm will take care of the rest, such as selecting the appropriate host on which to run the container.
Pro Communicates with other Docker tools easily
Since Docker Swarm is a native Docker tool, it exposes the Docker API, making it possible t integrate it and communicate with other Docker tools (CLI, Compose, Krane, etc.).
Docker Swarm is much more lightweight than alternatives: Kubernetes and Mesosphere. Kubernetes, for instance, is very complex - it downloads and installs half of the web, where Docker Swarm has much, much smaller footprint.
Pro Open source
Docker Swarm is open source and provides great guides/documentation for those who want to contribute.
Pro Compatible with Docker Compose
This gives you a well-rounded workflow.
Con If a node dies in the Swarm Cluster, the containers on that node WILL be started on a another node ...
Con Not fault tolerant
If a node dies in your cluster, the containers on that node won't be restarted
Con Bounded by the limitations of the Docker API
If the Docker API doesn't support something, then you are pretty much out of luck when it comes to Docker Swarm, because it won't be supported by Swarm either.