haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #6753 from sschuberth/master 

docs: Clarify that VirtualBox is not the only shipped provider
This commit is contained in:
Seth Vargo 2015-12-28 17:21:45 -05:00
parent 9a5597e1a7 992d2d70e7
commit e2a52144d6
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/source/v2/providers/index.html.md
View File

@ -6,6 +6,7 @@ sidebar_current: "providers"
# Providers # Providers
While Vagrant ships out of the box with support for [VirtualBox](http://www.virtualbox.org), While Vagrant ships out of the box with support for [VirtualBox](http://www.virtualbox.org),
[Hyper-V](http://www.microsoft.com/hyper-v) and [Docker](http://www.docker.io),
Vagrant has the ability to manage other types of machines as well. This is done Vagrant has the ability to manage other types of machines as well. This is done
by using other _providers_ with Vagrant. by using other _providers_ with Vagrant.
@ -14,9 +15,8 @@ For example, if you're using Vagrant for any real work, [VMware](http://www.vmwa
providers are recommended since they're well supported and generally more providers are recommended since they're well supported and generally more
stable and performant than VirtualBox. stable and performant than VirtualBox.
Before you can use another provider, you must install it. Vagrant only ships Before you can use another provider, you must install it. Installation of other providers
with VirtualBox support. Installation of other providers is done via the is done via the Vagrant plugin system.
Vagrant plugin system.
Once the provider is installed, usage is straightforward and simple, as Once the provider is installed, usage is straightforward and simple, as
you would expect with Vagrant. Read into the relevant subsections found in you would expect with Vagrant. Read into the relevant subsections found in