Vagrant is a tool for building and distributing development environments.
Ruby HTML PowerShell CSS Shell JavaScript
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.github CONTRIBUTING: Add missing URL in mailing list link May 17, 2018
bin Allow vagrantfile_name stub disable via environment variable Jul 18, 2018
contrib contrib/bash/ replaced -VAGRANTSLASH- with a literal sl… Jul 4, 2018
keys Use SSL and HTTPS links where appropriate Jan 25, 2016
lib Fix: `trigger` embedded plugin fails to exec scripts at paths contain… Aug 17, 2018
plugins Merge pull request #10123 from briancain/add-force-flag-reload Aug 17, 2018
scripts Update RELEASE Jun 14, 2016
tasks Use color Jul 9, 2015
templates Merge pull request #10037 from chrisroberts/e-vagrant-plugins-local Jul 27, 2018
test Merge pull request #10118 from briancain/TRIGGER-SPACE-PATH Aug 17, 2018
website Merge pull request #10127 from briancain/doc-hostname-etc-hosts Aug 17, 2018
.gitignore Add a custom path location to ignore Feb 28, 2018 Add simple build script Mar 7, 2018
.travis.yml Update Ruby test versions Jun 12, 2018
.vimrc .vimrc with vagrant tabstop settings Oct 22, 2013
.yardopts YARD and some documentation Sep 22, 2010 Update CHANGELOG Aug 17, 2018
Gemfile Update URLs for the repo Mar 7, 2018
LICENSE Update license year Jan 1, 2018 Update (and related stuff) May 16, 2018 Propose fix some typos Feb 6, 2018
Rakefile Change symbols inside hashes to 1.9 JSON-like syntax May 22, 2014
Vagrantfile Updated Vagrantfile to install more recent versions of software. Jul 27, 2016
vagrant-spec.config.example.rb core: Within a Bundler env, don't manage Bundler Jan 17, 2014
vagrant.gemspec Update net-ssh constraint Jul 27, 2018
version.txt Update version for dev Jun 26, 2018


Vagrant is a tool for building and distributing development environments.

Development environments managed by Vagrant can run on local virtualized platforms such as VirtualBox or VMware, in the cloud via AWS or OpenStack, or in containers such as with Docker or raw LXC.

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.

Quick Start

For the quick-start, we'll bring up a development machine on VirtualBox because it is free and works on all major platforms. Vagrant can, however, work with almost any system such as OpenStack, VMware, Docker, etc.

First, make sure your development machine has VirtualBox installed. After this, download and install the appropriate Vagrant package for your OS.

To build your first virtual environment:

vagrant init hashicorp/precise32
vagrant up

Note: The above vagrant up command will also trigger Vagrant to download the precise32 box via the specified URL. Vagrant only does this if it detects that the box doesn't already exist on your system.

Getting Started Guide

To learn how to build a fully functional development environment, follow the getting started guide.

Installing from Source

If you want the bleeding edge version of Vagrant, we try to keep master pretty stable and you're welcome to give it a shot. Please review the installation page here.

Contributing to Vagrant

Once your Vagrant bundle is installed from Git repository, you can run the test suite with:

bundle exec rake

This will run the unit test suite, which should come back all green!

Please take time to read the HashiCorp Community Guidelines and the Vagrant Contributing Guide.

Then you're good to go!

Acceptance Tests

Vagrant also comes with an acceptance test suite that does black-box tests of various Vagrant components. Note that these tests are extremely slow because actual VMs are spun up and down. The full test suite can take hours. Instead, try to run focused component tests.

To run the acceptance test suite, first copy vagrant-spec.config.example.rb to vagrant-spec.config.rb and modify it to valid values. The places you should fill in are clearly marked.

Next, see the components that can be tested:

$ rake acceptance:components

Then, run one of those components:

$ rake acceptance:run COMPONENTS="cli"