Vagrant is a tool for building and distributing development environments.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sophia 99fdfa1759 Update CHANGELOG 13 hours ago
.ci Set proper root dir path for sync script 1 month ago
.circleci Add Algolia index script to CI 1 month ago
.github Merge pull request #11405 from briancain/ci/add-gh-actions 1 month ago
bin Use :ui_class opt to set ui class 4 months ago
contrib Merge pull request #11520 from soapy1/zsh-completion 2 weeks ago
keys Use SSL and HTTPS links where appropriate 4 years ago
lib Merge pull request #11618 from jbonhag/fix/empty-box 19 hours ago
plugins Merge pull request #11809 from soapy1/fix-secure-boot 13 hours ago
scripts Update RELEASE 4 years ago
tasks Use color 5 years ago
templates Merge pull request #11618 from jbonhag/fix/empty-box 19 hours ago
test Merge pull request #11795 from LachlanArthur/smb-credential-check-2 13 hours ago
website Hyperv: moving session transport type config from string to boolean for enhanced mode aka HvSocker 1 day ago
.gitignore Add a custom path location to ignore 2 years ago
.hashibot.hcl Do not comment when locking really old issues 4 months ago Add simple build script 2 years ago
.vimrc .vimrc with vagrant tabstop settings 6 years ago
.yardopts YARD and some documentation 10 years ago Update CHANGELOG 13 hours ago
Gemfile Update URLs for the repo 2 years ago
LICENSE Update year on LICENSE 1 year ago remove internal '.html' extensions 2 months ago Update the steps in the release document 1 year ago
Rakefile Change symbols inside hashes to 1.9 JSON-like syntax 6 years ago
Vagrantfile Box switched to hashicorp/bionic64 and supported providers adjusted 10 months ago
vagrant-spec.config.example.rb core: Within a Bundler env, don't manage Bundler 6 years ago
vagrant.gemspec Bump version of net-ssh to ~> 6.0 and net-sftp to ~> 3.0 1 day ago
version.txt Update files for new development 3 months ago


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

Package dependencies: Vagrant requires bsdtar to be available on your system PATH to run successfully.

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/bionic64
vagrant up

Note: The above vagrant up command will also trigger Vagrant to download the bionic64 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!

If you are developing Vagrant on a machine that already has a Vagrant package installation present, both will attempt to use the same folder for their configuration (location of this folder depends on system). This can cause errors when Vagrant attempts to load plugins. In this case, override the VAGRANT_HOME environment variable for your development version of Vagrant before running any commands, to be some new folder within the project or elsewhere on your machine. For example, in Bash:

export VAGRANT_HOME=~/.vagrant-dev

You can now run Vagrant commands against the development version:

bundle exec vagrant

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"