Vagrant is a tool for building and managing virtual machine environments in a single workflow.

In order to support its growing ecosystem and community as we move toward the 3.0 release, we are making changes to Vagrant that will maintain its Ruby-based features while being ported to Go.

Toward Vagrant 3.0

Watch these highlighted talks from our 2021 HashiTalks community event. Our first recap features talks on HashiCorp Boundary, Packer, Vagrant, and Waypoint.

HashiTalks 2021 Highlights: Boundary, Packer, Vagrant, and Waypoint

We will be organizing a HashiCraft Holidays Hackstravaganza where you and your fellow tinkerers can use your creativity to showcase one or more of our products in creative and unexpected ways.

Announcing the HashiCraft Holidays Hackstravaganza

Get Terraform, Packer, Vault, Consul, and Nomad up and running even faster on macOS with our new official Homebrew Tap.

Announcing HashiCorp’s Homebrew Tap

The latest release of Vagrant comes with dependency provisioners and support for Vagrant box checksums in Vagrant Cloud. See how these features work in this release announcement.

What’s New In HashiCorp Vagrant 2.2.6

We are pleased to announce the release of Vagrant 2.2.0. Vagrant is a tool for building and distributing development environments. The highlight of this release is the introduction of Vagrant Cloud command line tool.

 Vagrant 2.2.0

We are pleased to announce the release of Vagrant 2.1.0. Vagrant is a tool for building and distributing development environments. The highlight of this release is the introduction of Vagrant triggers as a core feature.

HashiCorp Vagrant 2.1.0

We are pleased to announce the release of Vagrant 2.0.4. Vagrant is a tool for building and distributing development environments. The highlight of this release is a new alias feature for the Vagrant CLI.

HashiCorp Vagrant 2.0.4

We are pleased to announce the release of the Vagrant VMware Desktop plugin. This plugin is a unification of the Vagrant VMware Fusion plugin for macOS and the Vagrant VMware Workstation plugin for Linux and Windows. Existing users of the Vagrant VMware Fusion or Workstation plugins can update to the new VMware Desktop plugin free of charge. The new VMware Desktop plugin includes an updated implementation and installation process. This process addresses critical security issues that were found in prior versions. All users are recommended to install this update immediately.

Introducing the Vagrant VMware Desktop Plugin

We are pleased to announce the release of Vagrant 2.0.3. Vagrant is a tool for building and distributing development environments. This release contains many bug fixes and improvements.

HashiCorp Vagrant 2.0.3 

The Vagrant VMware plugin will fail to activate with HashiCorp servers
starting on February 18th, 2018. For the next 30 days after this date, currently installed VMware plugins will start to encounter errors activating their license.

Updating the Vagrant VMware Plugin

We are pleased to announce the release of HashiCorp Vagrant 2.0.2. Vagrant is a tool for building and distributing development environments. The highlight of this release is an updated implementation of SMB synced folders with added host support for macOS.

HashiCorp Vagrant 2.0.2.

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 2.0 is available immediately from the Vagrant website. You can find the full list of changes in recent Vagrant releases in the Changelog.

HashiCorp Vagrant 2.0

We are pleased to announce the release of HashiCorp Vagrant 1.9.6. This release includes many improvements and bug fixes.

Vagrant 1.9.6

Back in May, we announced our plans for the Vagrant Cloud migration. We are happy to announce today that the Vagrant Cloud Migration is complete and located at its new home app.vagrantup.com.

HashiCorp Vagrant Cloud Migration Completed

We are excited to announce that HashiCorp Vagrant features will be extracted from Atlas on June 27th into its own product, HashiCorp Vagrant Cloud. 
Features include:

Vagrant Box Creation to publish public or private Vagrant boxes for others to consume
Vagrant Box Versioning to update boxes and communicate these changes to consumers
Vagrant Box Catalog to search and discover public Vagrant boxes

Going forward, Vagrant Cloud will be developed independently, which allows us to improve current functionality and eventually provide new services around Vagrant.
If you only use Vagrant to download and run public boxes, then nothing is changing. All box names, versions, and URLs will stay the same (or redirect) with no changes to your workflow or Vagrantfiles.
Read more to learn about the migration of existing hosted Vagrant boxes and accounts.

Vagrant Cloud Migration Announcement

We are pleased to announce the release of Vagrant 1.9.5. This release includes new features, improvements, and bug fixes.
Download Vagrant 1.9.5 here

Vagrant 1.9.5

We are pleased to announce the release of Vagrant 1.9.4. This release
includes new features as well as many improvements and bug fixes. Download Vagrant 1.9.4 here.

Vagrant 1.9.4

We are pleased to announce the release of Vagrant v1.9.2. This release includes
several new features, improvements, and bug fixes.

Vagrant v1.9.2 released!

CVE-2015-7547 was announced on the morning of February 16th.  We would like to address HashiCorp users on how this affects any HashiCorp tooling.

glibc's CVE-2015-7547 and HashiCorp Tools

Today we announce the release of Vagrant 1.8. Vagrant is a tool for building and managing development environments.

Vagrant 1.8 introduces a number of major features and hundreds of improvements and bug fixes. The major features are outlined below and the full list of improvements can be found in the official CHANGELOG. Thanks to the hundreds of contributors that helped make this release bigger and better than it could've been with just us working on it.

You can download Vagrant 1.8 from the project website. There are no major backward incompatibilities so you should be able to drop-in the update and get working right away!

Read on to learn more about the major new features in Vagrant 1.8.

HashiCorp Vagrant 1.8

Project Photon by VMware is a container-optimized Linux operating system that was announced today. We have packaged it as a Vagrant box to make experimenting with Photon using Vagrant an easy and enjoyable process.

Vagrant Up and Running with VMware's Project Photon

Vagrant 1.7 comes with a new command: vagrant push. Just as vagrant up
is a single command to create a development environment for any application,
vagrant push is a single command to deploy any application.

The goal of Vagrant is to give developers a single workflow to develop
applications effectively. vagrant up creates a development environment for any
application and vagrant share enables collaboration for any application.
Deploying was the next logical step for Vagrant, now possible with
vagrant push.

Like every other component of Vagrant, push can be configured using multiple
strategies. vagrant push can deploy via FTP, Heroku,
Atlas, or by executing any local script.
Other strategies can be added via plugins and more will be added to core
as time goes on.

Read on to learn more.

Vagrant Push: One Command to Deploy Any Application

Vagrant 1.6 is now available! This is a new major release building upon Vagrant 1.5 to add new features to improve workflow, expand Vagrant to support more development environment types, and more.

Vagrant 1.6 introduces no breaking backwards compatibilities. There are some configuration options that have changed but they still work and will now just output deprecation warnings.

There are a few major features in Vagrant 1.6. We covered the major features in feature previews leading up to this release. You can find more information by clicking on the feature name below:

Global Status and Control

Windows Guests

Docker-Based Development Environments

You can download Vagrant now or read the complete CHANGELOG. Or, continue reading to get an overview of the new features and improvements in Vagrant 1.6, as well as the direction we're heading for Vagrant 1.7.

Vagrant 1.6

Vagrant 1.6 comes with a new built-in provider: Docker. The Docker provider allows Vagrant to manage development environments that run within containers, rather than virtual machines. This works without any additional software required on Linux, Mac OS X, and Windows.

The Docker provider in Vagrant makes it incredibly easy to keep the workflow you're used to with both Vagrant and Docker while gaining all the benefits of Vagrant: cross-platform portability, synced folders, networking, provisioners, vagrant share, plugins, etc.

On platforms that don't support Linux Containers natively such as Mac OS X and Windows, Vagrant automatically brings up and shares a proxy virtual machine to run Docker. This proxy VM is completely customizable, and Vagrant ensures that synced folders and networking work as you would expect. Users of Vagrant don't need to worry about doing any of this manually.

Read on to learn more.

Feature Preview: Docker-Based Development Environments

Vagrant 1.6 will add a monumental feature to Vagrant: full Windows guest support. The ability of Vagrant to manage Windows environments just as easy as Linux environments has been requested for years and the time for complete, official support has come.

Please don't mistake guest support for running Vagrant on Windows. Vagrant has fully supported running on Windows for years, and works great. Vagrant 1.6 adds support for Vagrant to run Windows within the Vagrant environments (in VirtualBox, Hyper-V, EC2, etc.).

The Windows guest support coming in Vagrant 1.6 allows you to spin up Windows environments just as easily as you would Linux environments, and lets you use PowerShell scripts, Chef, Puppet, etc. to install and configure software.

And just as Linux has vagrant ssh as a first-class citizen, Windows guests have vagrant rdp, which allow single-command access to a complete remote desktop environment to your Windows environment.

Read on to learn more.

Feature Preview: Windows Guests

Vagrant 1.5 was released just a month ago, but we already have big changes lined up for Vagrant 1.6. To prepare you for the release of 1.6, we're restarting our weekly "feature preview" blog post series to cover the new features that are on the way.

The first new feature we'll be covering is something we're calling global status and control.

Global status introduces a new global-status command to Vagrant that will show you the status of all created Vagrant environments on your system. You'll never again forget what Vagrant environments are running, not running, or using resources on your system.

Global control lets you use a unique ID assigned to each of your Vagrant environments to control it from any directory, not only the directory where the Vagrantfile is. This is useful in many situations, but perhaps this is most useful when you forget to destroy a Vagrant environment. You can now destroy that Vagrant environment from anywhere!

With these two features Vagrant environment management becomes much easier.

Read on to learn more.

Feature Preview: Global Status and Control

Vagrant 1.5 is now available! This is a new major release that adds some incredible new features to Vagrant. We've also obsessed over stability, so we expect this to be the most stable release, as well.

We're also announcing Vagrant Cloud, a place for sharing, discovering, and creating Vagrant environments.

Vagrant 1.5 and Vagrant Cloud

Vagrant has worked on Windows for over four years. Vagrant has worked well on Windows for about two years. With Vagrant 1.5, Vagrant is excellent on Windows with dozens of bug fixes and a couple big Windows-only features: Hyper-V and SMB synced folders.

Vagrant 1.5 will ship with a Hyper-V provider out of the box. This is big news! This is the first provider other than VirtualBox to ship with Vagrant itself (with more to come). And, Hyper-V comes built-in to almost all editions of Windows 8+, meaning Vagrant works with nothing more than a Windows computer for most people.

Additionally, Windows users have the option now to use SMB synced folders. SMB is a technology built right into Windows, just like Hyper-V, making it easy for Windows users to get high performance synced folders out of the box.

Read on to learn more about these features.

Feature Preview: Hyper-V, SMB Synced Folders, Windows

Vagrant has a vibrant plugin community. We're always looking to improve the life of a plugin developer through better abstractions, documentation, and more. In Vagrant 1.5, we made some big improvements that should make developing plugins much, much nicer.

With Vagrant 1.1, we both helped and hurt plugin development. Plugin development improved because plugins became a first class supported concept with the vagrant plugin command and much of the core dogfooding the API.

But plugin development was hurt because Vagrant switched to an installer-only model, breaking many plugin development environments and causing some frustrating edge cases.

With Vagrant 1.5, we've made some big changes that should make the life of a plugin developer much more enjoyable. Read on to find out more.

Plugin Development Improvements in Vagrant 1.5

A primary goal of Vagrant is not only to provide easy-to-use development environments, but also to make it easy to share and collaborate on these environments.

With Vagrant 1.5, we're introducing a feature that will allow you to share your running Vagrant environment with anyone, on any network connected to the internet. We're calling this feature 'Vagrant Share.'

This feature lets you share a link to your web server to a teammate across the country, or just across the office. It'll feel like they're accessing a normal website, but actually they'll be talking directly to your running Vagrant environment. They'll be able to see any changes you make, as you make them, in real time.

With Vagrant Share, others can not only access your web server, they can access your Vagrant environment like it was any other machine on a local network. They can have access to any and every port.

Read on for a demo and more details.

Vagrant 1.5 Feature Preview: Vagrant Share

Vagrant 1.5 will feature a revamped system for finding, downloading, and using boxes. With Vagrant 1.5 boxes will be easier than ever to find, build, use, update, and share. For new users, Vagrant becomes much easier to use, and for existing users, the box system becomes much more powerful with new features to help teams using Vagrant.

Here are some quick highlights of the new box system: box names are now as simple as hashicorp/precise64, which acts as both the address for the box as well as the name. A single box address can represent a box for multiple providers, so you no longer need to special-case box URLs depending on the provider in use. Boxes are now versionable, so you can deploy box updates and users of that box are notified when updates are available. And finally, we're launching a public service to share, discover, and build boxes.

And, we're also happy to say that the new system is fully backwards compatible. All old CLI commands, box files, and Vagrantfiles continue to behave exactly the way they have before.

Read on to learn more about how all these new features work as well as to learn some of the motivation behind the features.

Vagrant 1.5 Feature Preview: Boxes 2.0

Vagrant 1.5 is going to be the biggest release of Vagrant since 1.1, with dozens of new features and improvements coming in. Don't worry, we've also obsessed over stability, so we expect it'll be one of the most stable upgrades, too.
Because Vagrant 1.5 will be so feature-packed, we're doing a series of blog posts that highlight the upcoming features so you know what to look forward to and how to use them. These posts will be weekly on Wednesdays, so keep an eye out for them!
We're going to kick off the series by introducing rsync synced folders. These synced folders offer incredible I/O performance at the expense of a little bit of latency. Read on to learn more.

Vagrant 1.5 Feature Preview: Rsync Synced Folders

At nearly four years old, Vagrant is considered mature and stable software. Thousands of individuals depend on Vagrant every day to provide a stable working environment, crucial to their productivity. We pride ourselves on shipping software that can stand up to this requirement.
Even so, we've noticed an unacceptable trend of &amp;quot;upgrade pains&amp;quot; whenever a major new version of Vagrant is released. In every case, once Vagrant is working, it is very stable. However, after an upgrade, the fact some environments have to be &amp;quot;fixed&amp;quot; is not okay.
A big focus of the project for the past couple months has been improving
stability, especially upgrade stability. In this post, I'd like to discuss
some of the changes we've made so you can be confident that Vagrant upgrades
won't break things for you.

Vagrant Stability and Upgrades

Vagrant 1.4.2 has been released. This is a bug-fix release for Vagrant 1.4.x and is a safe drop-in upgrade for all Vagrant 1.4 users. Vagrant 1.4.2 can be downloaded today from the downloads page. The complete changelog for this release can be found here.

Vagrant 1.4.2

Vagrant 1.4.1 has been released. This is a bug-fix release for Vagrant 1.4.0 and is a safe drop-in upgrade for all Vagrant 1.4 users. Vagrant 1.4.0 has been the most stable release so far in the 1.x series and we're happy to make a bug-fix release to make it even more reliable.

Vagrant 1.4.1 can be downloaded today from the downloads page. The complete changelog for this release can be found here.

One notable improvement is that the Docker provisioner now works with RedHat-based guest machines. The remainder of changes are bug fixes.

Vagrant 1.4.1

Vagrant 1.4 has been released! This is a major new release of Vagrant with an incredible amount of new features, improvements, and bug fixes. Vagrant 1.4 can be downloaded on our new downloads page.

First, I have to thank the new core committers of Vagrant for building many of the incredible features and improvements that made it into this release: Fabio Rehm, Paul Hinze, and Teemu Matilainen.

Vagrant 1.4 introduces no Vagrantfile backwards incompatibilities so it can be considered a drop-in upgrade for prior versions. Vagrant environments also do not need to be destroyed prior to upgrading.

There are a huge number of new features introduced in Vagrant 1.4, and this blog post will attempt to cover the major ones. For all changes see the changelog.

Vagrant 1.4

Today, we're announcing support for VMware Workstation in addition to the VMware Fusion support we announced in March.

Workstation is the desktop virtualization solution that VMware provides for Linux and Windows machines. The integration with Vagrant will allow you to run the same virtual machines in VMware across Mac OS X, Linux, and Windows.

VMware technology offers improved performance, stability, and support for those who want it, and the Vagrant integration lets you keep the same great Vagrant workflow.

The workstation provider is available now for the same price as the Fusion provider: $79 per seat. The provider will work on both Linux and Windows. In Windows, Vagrant works in cmd.exe, PowerShell, Cygwin, and MSYS/MingW environments.

VMware Workstation

I'm happy to announce the release and immediate availability of Vagrant 1.1 and the long-awaited VMware Fusion provider, allowing you to use Vagrant to control machines on top of the rock solid, ultra performant VMware hypervisor.

This release introduces the concept of providers, which allows Vagrant to control machines on systems other than VirtualBox. This marks the beginning of a new era for Vagrant, an era unconstrained by the limitations of any specific provider.

The VMware Fusion provider is the first paid add-on for Vagrant from HashiCorp. The Fusion provider has already been in use with great success by hundreds of early testers looking for improved stability and performance from their Vagrant environments.

Open source providers for AWS and RackSpace are also available today.

Vagrant 1.1 can be downloaded immediately from the Vagrant website. The Fusion provider can be purchased immediately from the VMware Fusion provider page.

Vagrant 1.1, VMware Fusion

Sponsored by Vocalocity, HashiCorp has developed a fully open-source, MIT licensed AWS provider plugin for Vagrant 1.1.

Using the same Vagrant workflow you've come to know and love, you will be able to launch and provision instances in EC2 or VPC, just as you would a VirtualBox machine today.

Paired with local virtualization, the AWS provider can vastly improve your end-to-end workflow, unlocking use cases for Vagrant which simply didn't exist before.

The provider will be released as open source at the same time as Vagrant 1.1, and works on Mac, Windows, and Linux. While no release date has been set, Vagrant 1.1 is targeted for later this month.

Preview: Vagrant AWS Provider

To kick off the new year, Vagrant has a brand new look! Vagrant has a new logo for the first time in three years, and the website is redesigned and restructured.

The new Vagrant logo is a simple "V" built up with isometric cubes. This matches the core HashiCorp style, visible on the HashiCorp homepage. The old logo or mascot, known as "Vince," is now retired.

The main website has been completely redesigned and incorporates the new logo.