5 thoughts on “What is the use of vagrant?”

  1. It helps automate some drudgery with VMs and allows you to restore to a base rapidly or create many VMs from the same base. It can be useful in both development and testing but is not intended for “production” like scenarios where things like docker or configuration management tools (like Ansible, Chef) are more appropriate.

    In fact, one of my primary uses for Vagrant is to develop and test my configuration management scripts.

  2. Vagrant is a simple tool for building virtual machines. It includes a distribution mechanism for VM images, and automates the process of creating a VM from one of the images.

    A lot of the things we used to use Vagrant for are now easier to do on Docker. But there are some situations where a virtual machine is still the right answer, and vagrant is a fantastic tool for those use cases.

    * Kernel testing/development
    * Windows and other non-linux operating systems
    * Direct hardware access (relevant for Windows and OSX docker users)
    * Enhanced software isolation

  3. Vagrant creates VMs using a base box from their repository. Paired with easy to use file sharing from the host environment makes it very good for building development machines.

    On Windows (and other places) this is mostly moving to docker containers, but Vagrant has been a very very good option.

  4. Makes it easy to create a standardized development environment for a team. No more time lost because half the team doesn’t have the right dependencies installed on their individual machines.

    Just like standardizing VMs and containers in the cloud prevents snowflaking, but for dev and test environments.


Leave a Comment