2013-09-03 18:08:28 +00:00
|
|
|
---
|
2016-01-19 18:08:53 +00:00
|
|
|
layout: "docs"
|
2013-09-06 16:50:43 +00:00
|
|
|
page_title: "Providers"
|
2013-09-03 18:08:28 +00:00
|
|
|
sidebar_current: "providers"
|
2016-01-19 18:08:53 +00:00
|
|
|
description: |-
|
|
|
|
While Vagrant ships out of the box with support for VirtualBox, Hyper-V, and
|
|
|
|
Docker. Vagrant has the ability to manage other types of machines as well.
|
|
|
|
This is done by using other providers with Vagrant.
|
2013-09-03 18:08:28 +00:00
|
|
|
---
|
|
|
|
|
|
|
|
# Providers
|
|
|
|
|
2016-01-19 18:08:53 +00:00
|
|
|
While Vagrant ships out of the box with support for [VirtualBox](https://www.virtualbox.org),
|
|
|
|
[Hyper-V](https://www.microsoft.com/hyper-v), and [Docker](https://www.docker.io),
|
2013-09-03 18:08:28 +00:00
|
|
|
Vagrant has the ability to manage other types of machines as well. This is done
|
|
|
|
by using other _providers_ with Vagrant.
|
|
|
|
|
|
|
|
Alternate providers can offer different features that make more sense in your use case.
|
2016-01-19 18:08:53 +00:00
|
|
|
For example, if you are using Vagrant for any real work, [VMware](https://www.vmware.com)
|
2013-09-03 18:08:28 +00:00
|
|
|
providers are recommended since they're well supported and generally more
|
|
|
|
stable and performant than VirtualBox.
|
|
|
|
|
2015-12-28 21:57:40 +00:00
|
|
|
Before you can use another provider, you must install it. Installation of other providers
|
|
|
|
is done via the Vagrant plugin system.
|
2013-09-03 18:08:28 +00:00
|
|
|
|
|
|
|
Once the provider is installed, usage is straightforward and simple, as
|
|
|
|
you would expect with Vagrant. Read into the relevant subsections found in
|
|
|
|
the navigation to the left for more information.
|