3 ms·
Vagrant is useful if you want to simulate a whole box, or a cluster of boxes - for example, you can spin up a cluster of 3 VMs to run Mesosphere DC/OS [0]. If y
by jitl 9y ago
Vagrant is useful if you want to simulate a whole box, or a cluster of boxes - for example, you can spin up a cluster of 3 VMs to run Mesosphere DC/OS [0]. If you build and deploy just containers, and don't have any full VMs in your stack, then you might not need Vagrant.
Vagrant also claims to provide a "good workflow for writing Dockerfiles"; it can provide a nicer user abstraction over `docker [many, many args]` for running your biz [1].
[0]: https://github.com/dcos/dcos-vagrant#dcos-vagrant https://github.com/dcos/dcos-vagrant#dcos-vagrant
[1]: https://www.vagrantup.com/docs/docker/basics.html https://www.vagrantup.com/docs/docker/basics.html
- valfadeev 9y agoThis is exactly where I began getting the most out of Vagrant, that is, simulating a distributed cluster locally. It gets me as close as possible to how it would work on the provider infrastructure, e.g. AWS. In particular, spinning up an automated Consul cluster and then using it get a group of RabbitMQ nodes to converge[0]. The same is certainly achievable through container orchestration, but that adds more layers of abstraction, especially on the networking side. [0]: https://github.com/ValFadeev/consul-demo https://github.com/ValFadeev/consul-demo