vagrant/website/content/docs/providers/index.mdx
2025-11-20 12:41:04 -05:00

32 lines
1.8 KiB
Text

---
layout: docs
page_title: Providers
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.
---
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
> [!IMPORTANT]
> **Documentation Update:** Product documentation previously located in `/website` has moved to the [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs) repository, where all product documentation is now centralized. Please make contributions directly to `web-unified-docs`, since changes to `/website` in this repository will not appear on developer.hashicorp.com.
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
# Providers
While Vagrant ships out of the box with support for [VirtualBox](https://www.virtualbox.org),
[Hyper-V](https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/about/), and [Docker](https://www.docker.io),
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.
For example, if you are using Vagrant for any real work, [VMware](https://www.vmware.com)
providers are recommended since they're well supported and generally more
stable and performant than VirtualBox.
Before you can use another provider, you must install it. Installation of other providers
is done via the Vagrant plugin system.
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.