Rancher vs Vagrant: What are the differences?
Rancher: Open Source Platform for Running a Private Container Service. Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform; Vagrant: A tool for building and distributing development environments. Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux.
Rancher and Vagrant are primarily classified as "Container" and "Virtual Machine Management" tools respectively.
Some of the features offered by Rancher are:
- Manage Hosts, Deploy Containers, Monitor Resources
- User Management & Collaboration
- Native Docker APIs & Tools
On the other hand, Vagrant provides the following key features:
- Up And SSH
- Synced Folders
"Easy to use", "Open source and totally free" and "Multi-host docker-compose support" are the key factors why developers consider Rancher; whereas "Development environments", "Simple bootstraping" and "Free" are the primary reasons why Vagrant is favored.
Rancher and Vagrant are both open source tools. Vagrant with 18.6K GitHub stars and 3.74K forks on GitHub appears to be more popular than Rancher with 11.9K GitHub stars and 1.34K GitHub forks.
Airbnb, Shopify, and Coursera are some of the popular companies that use Vagrant, whereas Rancher is used by Redox Engine, Packet, and VCCloud. Vagrant has a broader approval, being mentioned in 802 company stacks & 478 developers stacks; compared to Rancher, which is listed in 89 company stacks and 35 developer stacks.
What is Rancher?
What is Vagrant?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
- Consume too much unnecessary resource by just running rancher agent alone;
- Hard to recover from system failure
- Bad performance of load balancing (compare to dokcer swarm built-in LB or others).
"The best way to ensure that local testing was possible was to normalize people’s dev environments. For this we chose Vagrant. This, combined with Chef, allows us to do our local dev in sandboxed Linux instances running locally via VirtualBox in a configuration as similar to production as possible. In addition to making dev environment setup much easier than it used to be, this ensures that each engineer has a consistent environment that is ready to run tests out of the box. The user SSHs into the local linux server and runs spec commands like they would on their host OS, and generally everything Just Works. Most people on our team combine this with Zeus, which allows the Rails environment to be preloaded for lightning fast (relatively speaking) test runs. Both Vagrant and Zeus have their share of issues, but in practice we’ve found them to be a huge time saver."
Not blazing fast but we pick Vagrant for all our projects because the console mode without gui leads to a low consumption of ram memory making it the best way for DevOps ready environment requiring less configuration.
Vagrant allows me to ensure that anyone I'm collaborating with will be able to test my web application in the same environment. I also use Vagrant to setup VMs that I can use to refine my Capistrano recipes.
We use Virtualbox in combination with Vagrant during development to ensure a consistent test/development environment. This helps to reduce the number of defects when our software goes to production.
The whole infrastructure is managed through Rancher. It provides a simple interface to all the underlying tools - Docker, HAProxy (automatically configures load balancer from the containers).
Building development environments that closely match real world web environments, enabling more rapid and accurate testing and development.
Currently looking to move to Swarm or Kubernetes due to a few issues I have with Rancher.
Orchestration of containers for our environments. Remote deployment from Jenkins.
We use Rancher for container orchestration and automated deployment pipelines.