We're announcing HashiCorp Vagrant 2.0. Vagrant is a tool for building and distributing development environments.
Vagrant 2.0 supports provisioning development environments on VirtualBox, VMware, Hyper-V, Docker, AWS, GCP, and more. It can virtualize Windows, macOS, and a dozen other new operating systems. Vagrant 2.0 is paired with Vagrant Cloud for finding and consuming boxes. It has come a long way since Vagrant 1.0 when it only supported VirtualBox, and the community has grown significantly since then.
Vagrant was started in 2009 and quickly became a go-to tool for development environments and infrastructure automation development. The goal of Vagrant is to create a single workflow to build development infrastructures that mirror production.
Vagrant 1.0 was released in 2013 as a stable release. Vagrant 1.0 only supported VirtualBox as a provider, only supported a handful of Linux operating systems as guests, and supported a simple up/destroy workflow. Since Vagrant 1.0, we've added support for multi-providers such as VMware and Docker, guests such as Windows, macOS, and complex workflows including snapshots. These major changes are followed by hundreds of improvements and bug fixes.
Prior to Vagrant, development environments were primarily manually made, error prone, and time consuming. Infrastructure automation development had extremely long feedback cycles as real machines were created and destroyed. Vagrant turns both of these processes into a single command.
Vagrant is part of the HashiCorp product suite that enables you to provision, secure, connect and run any infrastructure for any application. You can provision development environments with Vagrant, build Vagrant images using HashiCorp Packer, launch infrastructure using HashiCorp Terraform, handle secrets management with Vault, schedule workloads with Nomad, and connect your infrastructure using Consul.
We want to thank our community and the Vagrant core team for bringing Vagrant to 2.0! HashiCorp Vagrant has over 750 contributors since it began 7 years ago. These contributors have added features, fixed bugs, and helped Vagrant move forward for years.
Due to the large surface area of compatibility Vagrant has to maintain, the project relies on the community to make the necessary improvements. Our community is filled with experts for every type of provider, every operating system, every provisioner, and more. These community members together create the versatile tool that is Vagrant.
At HashiCorp, Chris Roberts has led the charge towards 2.0. He became project lead of the project in 2016 and was tasked with completing the important stability work necessary to achieve version 2.0. Chris is joined by Brian Cain and Justin Campbell. Together, these three make sure Vagrant continues to progress every day.
Before we ring in the new year, here’s a look back at some of the most important moments in 2022 for HashiCorp.
HashiCorp Vagrant 2.3 introduces a new Vagrant executable written in Golang, tying the Vagrant architecture more closely into the broader HashiCorp ecosystem.
The HashiCorp Releases API is now available. This API is your one-stop shop for finding and viewing extended metadata about HashiCorp product releases.