mirror of
https://github.com/hashicorp/vagrant.git
synced 2026-06-04 14:22:22 -04:00
feat(website): migrates nav data format and updates docs pages (#12259)
This commit is contained in:
Bryce Kalow
GitHub
parent
b42cf83a88
commit
2c3397c468
203 changed files with 1350 additions and 506 deletions
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Creating a Base Box
|
||||
sidebar_title: Creating a Base Box
|
||||
description: |-
|
||||
There are a special category of boxes known as "base boxes." These boxes
|
||||
contain the bare minimum required for Vagrant to function, are generally
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Box File Format
|
||||
sidebar_title: Box File Format
|
||||
description: |-
|
||||
The box file format for Vagrant has changed from only supporting VirtualBox to
|
||||
supporting a number different providers and box formats.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Boxes
|
||||
sidebar_title: Boxes
|
||||
description: |-
|
||||
Boxes are the package format for Vagrant environments. A box can be used by
|
||||
anyone on any platform that Vagrant supports to bring up an identical
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Box Info Format
|
||||
sidebar_title: Box Info Format
|
||||
description: |-
|
||||
A box can provide additional information to the user by supplying an info.json
|
||||
file within the box.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Box Versioning
|
||||
sidebar_title: Box Versioning
|
||||
description: |-
|
||||
Since Vagrant 1.5, boxes support versioning. This allows the people who
|
||||
make boxes to push updates to the box, and the people who use the box
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Aliases - Command-Line Interface
|
||||
sidebar_title: Aliases
|
||||
description: |-
|
||||
Custom Vagrant commands can be defined using aliases, allowing for a simpler,
|
||||
easier, and more familiar command line interface.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant box - Command-Line Interface
|
||||
sidebar_title: box
|
||||
description: |-
|
||||
The "vagrant box" command is used to manage "vagrant box add", "vagrant box
|
||||
remove", and other box-related commands such as "outdated", "list", and
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant cloud - Command-Line Interface
|
||||
sidebar_title: cloud
|
||||
description: |-
|
||||
The "vagrant cloud" command can be used for taking actions against
|
||||
Vagrant Cloud like searching or uploading a Vagrant Box
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant connect - Command-Line Interface
|
||||
sidebar_title: connect
|
||||
description: |-
|
||||
The "vagrant connect" command compliments the "vagrant share" command to allow
|
||||
a user to remotely connect to your Vagrant environment.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant destroy - Command-Line Interface
|
||||
sidebar_title: destroy
|
||||
description: |-
|
||||
The "vagrant destroy" command is used to stop the running virtual machine and
|
||||
terminate use of all resources that were in use by that machine.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant global-status - Command-Line Interface
|
||||
sidebar_title: global-status
|
||||
description: |-
|
||||
The "vagrant global-status" command is used to determine the state of all
|
||||
active Vagrant environments on the system for the currently logged in user.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant halt - Command-Line Interface
|
||||
sidebar_title: halt
|
||||
description: |-
|
||||
The "vagrant halt" command is used to shut down the virtual machine that
|
||||
Vagrant is currently managing.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Command-Line Interface
|
||||
sidebar_title: Commands (CLI)
|
||||
description: Almost all interaction with Vagrant is done via the command-line interface.
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant init - Command-Line Interface
|
||||
sidebar_title: init
|
||||
description: |-
|
||||
The "vagrant init" command is used to initialize the current directory to be
|
||||
a Vagrant environment by creating an initial Vagrantfile.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant login - Command-Line Interface
|
||||
sidebar_title: login
|
||||
description: |-
|
||||
The "vagrant login" command is used to authenticate Vagrant with HashiCorp's
|
||||
Vagrant Cloud service to use features like private boxes and "vagrant push".
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Machine Readable Output - Command-Line Interface
|
||||
sidebar_title: Machine Readable Output
|
||||
description: |-
|
||||
Almost all commands in Vagrant accept a --machine-readable flag to enable
|
||||
machine-readable output mode.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: More Vagrant Commands - Command-Line Interface
|
||||
sidebar_title: More Commands
|
||||
description: |-
|
||||
In addition to the commands listed in the sidebar and shown in "vagrant -h",
|
||||
Vagrant comes with some more commands that are hidden from basic help output.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant package - Command-Line Interface
|
||||
sidebar_title: package
|
||||
description: |-
|
||||
The "vagrant package" command is used to package a currently-running
|
||||
VirtualBox or Hyper-V vagrant environment into a reusable Vagrant box.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant plugin - Command-Line Interface
|
||||
sidebar_title: plugin
|
||||
description: |-
|
||||
The "vagrant plugin" command is used to manage Vagrant plugins including
|
||||
installing, uninstalling, and license management.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant port - Command-Line Interface
|
||||
sidebar_title: port
|
||||
description: |-
|
||||
The "vagrant port" command is used to display the full list of guest ports
|
||||
mapped to the host machine ports.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant powershell - Command-Line Interface
|
||||
sidebar_title: powershell
|
||||
description: |-
|
||||
The "vagrant powershell" command is used to open a powershell prompt running
|
||||
inside the guest machine.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant provision - Command-Line Interface
|
||||
sidebar_title: provision
|
||||
description: |-
|
||||
The "vagrant provision" command is used to run any provisioners configured
|
||||
for the guest machine, such as Puppet, Chef, Ansible, Salt, or Shell.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant rdp - Command-Line Interface
|
||||
sidebar_title: rdp
|
||||
description: |-
|
||||
The "vagrant rdp" command is used to start an RDP client for a remote desktop
|
||||
session with the guest machine.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant reload - Command-Line Interface
|
||||
sidebar_title: reload
|
||||
description: |-
|
||||
The "vagrant reload" command is the equivalent of running "vagrant halt"
|
||||
followed by "vagrant up".
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant resume - Command-Line Interface
|
||||
sidebar_title: resume
|
||||
description: |-
|
||||
The "vagrant resume" command is used to bring a machine back into the "up"
|
||||
state, perhaps if it was previously suspended via "vagrant halt" or "vagrant
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant share - Command-Line Interface
|
||||
sidebar_title: share
|
||||
description: |-
|
||||
The "vagrant share" command initializes a new Vagrant share session, which
|
||||
allows you to share your virtual machine with the public Internet.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant snapshot - Command-Line Interface
|
||||
sidebar_title: snapshot
|
||||
description: |-
|
||||
The "vagrant snapshot" command is used to manage snapshots of the guest
|
||||
machine.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant ssh - Command-Line Interface
|
||||
sidebar_title: ssh
|
||||
description: |-
|
||||
The "vagrant ssh" command is used to establish an SSH session into a running
|
||||
virtual machine to give you shell access.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant ssh-config - Command-Line Interface
|
||||
sidebar_title: ssh-config
|
||||
description: |-
|
||||
The "vagrant ssh-config" command is used to output a valid SSH configuration
|
||||
file capable of SSHing into the guest machine directly.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant status - Command-Line Interface
|
||||
sidebar_title: status
|
||||
description: |-
|
||||
The "vagrant status" command is used to tell you the status of the virtual
|
||||
machines in the current Vagrant environment.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant suspend - Command-Line Interface
|
||||
sidebar_title: suspend
|
||||
description: |-
|
||||
The "vagrant suspend" command is used to suspend the guest machine Vagrant is
|
||||
currently managing.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant up - Command-Line Interface
|
||||
sidebar_title: up
|
||||
description: |-
|
||||
The "vagrant up" command is used to create, configuration, and provision a
|
||||
guest machine according to your Vagrantfile.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant upload - Command-Line Interface
|
||||
sidebar_title: upload
|
||||
description: |-
|
||||
The "vagrant upload" command is used to upload files from the host
|
||||
to a guest machine.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant validate - Command-Line Interface
|
||||
sidebar_title: validate
|
||||
description: The "vagrant validate" command is used to validate your Vagrantfile.
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: vagrant version - Command-Line Interface
|
||||
sidebar_title: version
|
||||
description: |-
|
||||
The "vagrant version" command is used to output the version of Vagrant
|
||||
currently installed on the system.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Vagrant Cloud-Init Configuration
|
||||
sidebar_title: Configuration
|
||||
description: Documentation of various configuration options for Vagrant cloud-init
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Cloud-Init
|
||||
sidebar_title: Cloud-Init
|
||||
description: Introduction to using cloud-init with Vagrant
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Vagrant Cloud-Init Usage
|
||||
sidebar_title: Usage
|
||||
description: Various Vagrant Cloud-Init examples
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Vagrant Disks Configuration
|
||||
sidebar_title: Configuration
|
||||
description: Documentation of various configuration options for Vagrant Disks
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Common Issues - Disks Hyper-V Provider
|
||||
sidebar_title: Common Issues
|
||||
description: |-
|
||||
This page lists some common issues people run into with Vagrant and Hyper-V
|
||||
as well as solutions for those issues.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Disks for Hyper-V Provider
|
||||
sidebar_title: Hyper-V
|
||||
description: |-
|
||||
Vagrant comes with support out of the box for Hyper-V, a free,
|
||||
cross-platform consumer virtualization product.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Usage - Disks Hyper-V Provider
|
||||
sidebar_title: Usage
|
||||
description: |-
|
||||
The Vagrant Hyper-V provider is used just like any other provider. Please
|
||||
read the general basic usage page for providers.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Vagrant Disks
|
||||
sidebar_title: Disks
|
||||
description: Introduction to Vagrant Disks
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Vagrant Disk Usage
|
||||
sidebar_title: Usage
|
||||
description: Various Vagrant Disk examples
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Common Issues - Disks VirtualBox Provider
|
||||
sidebar_title: Common Issues
|
||||
description: |-
|
||||
This page lists some common issues people run into with Vagrant and VirtualBox
|
||||
as well as solutions for those issues.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Disks for VirtualBox Provider
|
||||
sidebar_title: VirtualBox
|
||||
description: |-
|
||||
Vagrant comes with support out of the box for VirtualBox, a free,
|
||||
cross-platform consumer virtualization product.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Usage - Disks VirtualBox Provider
|
||||
sidebar_title: Usage
|
||||
description: |-
|
||||
The Vagrant VirtualBox provider is used just like any other provider. Please
|
||||
read the general basic usage page for providers.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Common Issues - Disks VMWare Provider
|
||||
sidebar_title: Common Issues
|
||||
description: |-
|
||||
HashiCorp develops an official VMware Fusion and VMware Workstation provider
|
||||
for Vagrant. This provider allows Vagrant to power VMware based machines and
|
||||
|
|
@ -23,13 +22,13 @@ disks options.
|
|||
## How many disks can I attach?
|
||||
|
||||
Vagrant will attempt to attach all disks specified in the Vagrantfile. If more than
|
||||
four `ide` type disks are specified, only the first four will be attached.
|
||||
four `ide` type disks are specified, only the first four will be attached.
|
||||
|
||||
## Applying Vagrant disk configuration changes to guests
|
||||
|
||||
Due to how VMware works, you must reload your guest for any disk config changes
|
||||
to be applied. So if you update your Vagrantfile to update or even remove disks, make
|
||||
sure to `vagrant reload` your guests for these changes to be applied. Also note, that
|
||||
sure to `vagrant reload` your guests for these changes to be applied. Also note, that
|
||||
Vagrant will not decrease the size of a disk.
|
||||
|
||||
## Disk functionality with snapshots
|
||||
|
|
@ -37,6 +36,6 @@ Vagrant will not decrease the size of a disk.
|
|||
If snapshots exist for a VM, disk functionality will be limited. Vagrant will return
|
||||
an error for any actions that are limited due to the existence of snapshots. In order
|
||||
to restore functionality the snapshots must be removed. This can be done using the
|
||||
[`vagrant snapshot delete`](/docs/cli/snapshot) command. To delete all snapshots
|
||||
[`vagrant snapshot delete`](/docs/cli/snapshot) command. To delete all snapshots
|
||||
for a VMWare backed VM try `vagrant cap provider delete_all_snapshots --target <target vm name>`.
|
||||
Note once a snapshot is deleted, it can not be restored.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Disks for VMWare Provider
|
||||
sidebar_title: VMWare
|
||||
description: |-
|
||||
HashiCorp develops an official VMware Fusion and VMware Workstation provider
|
||||
for Vagrant. This provider allows Vagrant to power VMware based machines and
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Usage - Disks VMWare Provider
|
||||
sidebar_title: Usage
|
||||
description: |-
|
||||
HashiCorp develops an official VMware Fusion and VMware Workstation provider
|
||||
for Vagrant. This provider allows Vagrant to power VMware based machines and
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Vagrant Experimental Feature Flag
|
||||
sidebar_title: Experimental
|
||||
description: Introduction to Vagrants Experimental Feature Flag
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Documentation
|
||||
sidebar_title: Overview
|
||||
description: |-
|
||||
Welcome to the documentation for Vagrant - the command line utility for
|
||||
managing the lifecycle of virtual machines. This website aims to document
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Backwards Compatibility
|
||||
sidebar_title: Backwards Compatibility
|
||||
description: Vagrant makes a very strict backwards-compatibility promise.
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Installing Vagrant
|
||||
sidebar_title: Installation
|
||||
description: |-
|
||||
Installing Vagrant is extremely easy. Head over to the Vagrant downloads page
|
||||
and get the appropriate installer or package for your platform. Install the
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Installing Vagrant from Source
|
||||
sidebar_title: From Source
|
||||
description: |-
|
||||
Installing Vagrant from source is an advanced topic and is only recommended
|
||||
when using the official installer is not an option. This page details the
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Uninstalling Vagrant
|
||||
sidebar_title: Uninstallation
|
||||
description: |-
|
||||
Uninstalling Vagrant is easy and straightforward. You can either uninstall
|
||||
the Vagrant binary, the user data, or both. The sections below cover how to
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Upgrading from Vagrant 1.0
|
||||
sidebar_title: Upgrading from 1.0.x
|
||||
description: |-
|
||||
The upgrade process from 1.0.x to 1.x is straightforward. Vagrant is
|
||||
backwards compatible with Vagrant 1.0.x, so you can simply reinstall Vagrant
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Upgrading Vagrant
|
||||
sidebar_title: Upgrading
|
||||
description: |-
|
||||
If you are upgrading from Vagrant 1.0.x, please read the specific page
|
||||
dedicated to that. This page covers upgrading Vagrant in general during the
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Multi-Machine
|
||||
sidebar_title: Multi-Machine
|
||||
description: |-
|
||||
Vagrant is able to define and control multiple guest machines per
|
||||
Vagrantfile. This is known as a "multi-machine" environment.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Basic Usage - Networking
|
||||
sidebar_title: Basic Usage
|
||||
description: |-
|
||||
Vagrant offers multiple options for how you are able to connect your
|
||||
guest machines to the network, but there is a standard usage pattern as
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Forwarded Ports - Networking
|
||||
sidebar_title: Forwarded Ports
|
||||
description: |-
|
||||
Vagrant forwarded ports allow you to access a port on your host machine and
|
||||
have all data forwarded to a port on the guest machine, over either TCP or
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Networking
|
||||
sidebar_title: Networking
|
||||
description: |-
|
||||
In order to access the Vagrant environment created, Vagrant exposes
|
||||
some high-level networking options for things such as forwarded ports,
|
||||
|
|
@ -39,14 +38,13 @@ with the Vagrant workflow and have things working at a basic level.
|
|||
Provider-specific network configuration can very quickly lock you out
|
||||
of your guest machine if improperly done.
|
||||
|
||||
|
||||
## Networking Assumptions
|
||||
|
||||
### There is a NAT availble
|
||||
|
||||
Vagrant assumes there is an available NAT device on eth0. This ensures
|
||||
that Vagrant always has a way of communicating with the guest machine.
|
||||
It is possible to change this manually (outside of Vagrant), however,
|
||||
this may lead to inconsistent behavior.
|
||||
that Vagrant always has a way of communicating with the guest machine.
|
||||
It is possible to change this manually (outside of Vagrant), however,
|
||||
this may lead to inconsistent behavior.
|
||||
Providers might have additional assumptions. For example, in VirtualBox,
|
||||
this assumption means that network adapter 1 is a NAT device.
|
||||
this assumption means that network adapter 1 is a NAT device.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Private Networks - Networking
|
||||
sidebar_title: Private Network
|
||||
description: |-
|
||||
Vagrant private networks allow you to access your guest machine by some
|
||||
address that is not publicly accessible from the global internet. In general,
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Public Networks - Networking
|
||||
sidebar_title: Public Network
|
||||
description: |-
|
||||
Vagrant public networks are less private than private networks, and the exact
|
||||
meaning actually varies from provider to provider, hence the ambiguous
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Debugging and Troubleshooting
|
||||
sidebar_title: Debugging
|
||||
description: |-
|
||||
As much as we try to keep Vagrant stable and bug free, it is inevitable
|
||||
that issues will arise and Vagrant will behave in unexpected ways. In
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Environmental Variables
|
||||
sidebar_title: Environmental Variables
|
||||
description: |-
|
||||
Vagrant has a set of environmental variables that can be used to
|
||||
configure and control it in a global way. This page lists those environmental
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Other
|
||||
sidebar_title: Other
|
||||
description: |-
|
||||
This page covers Vagrant information that does not quite fit under the other
|
||||
categories.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Vagrant and Windows Subsystem for Linux
|
||||
sidebar_title: WSL
|
||||
description: |-
|
||||
An overview of using Vagrant on Windows within the Windows Subsystem
|
||||
for Linux.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Plugin Development Basics - Action Hooks
|
||||
sidebar_title: Action Hooks
|
||||
description: |-
|
||||
Action hooks provide ways to interact with Vagrant at a very low level by
|
||||
injecting middleware in various phases of Vagrant's lifecycle. This is an
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Command Plugins - Plugin Development
|
||||
sidebar_title: Commands
|
||||
description: |-
|
||||
This page documents how to add new commands to Vagrant, invocable
|
||||
via "vagrant YOUR-COMMAND". Prior to reading this, you should be familiar
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Custom Configuration - Plugin Development
|
||||
sidebar_title: Configuration
|
||||
description: |-
|
||||
This page documents how to add new configuration options to Vagrant,
|
||||
settable with "config.YOURKEY" in Vagrantfiles. Prior to reading this,
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Plugin Development Basics - Plugins
|
||||
sidebar_title: Plugin Development Basics
|
||||
description: |-
|
||||
Plugins are a great way to augment or change the behavior and functionality
|
||||
of Vagrant. Since plugins introduce additional external dependencies for
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Guest Capabilities - Plugin Development
|
||||
sidebar_title: Guest Capabilities
|
||||
description: |-
|
||||
This page documents how to add new capabilities for guests to Vagrant,
|
||||
allowing Vagrant to perform new actions on specific guest operating systems.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Custom Guests - Plugin Development
|
||||
sidebar_title: Guests
|
||||
description: |-
|
||||
This page documents how to add new guest OS detection to Vagrant, allowing
|
||||
Vagrant to properly configure new operating systems. Prior to reading this,
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Host Capabilities - Plugin Development
|
||||
sidebar_title: Host Capabilities
|
||||
description: >-
|
||||
This page documents how to add new capabilities for hosts to Vagrant, allowing
|
||||
Vagrant to perform new actions on specific host operating systems. Prior to
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Custom Hosts - Plugin Development
|
||||
sidebar_title: Hosts
|
||||
description: |-
|
||||
This page documents how to add new host OS detection to Vagrant, allowing
|
||||
Vagrant to properly execute host-specific operations on new operating systems.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Plugins
|
||||
sidebar_title: Plugins
|
||||
description: |-
|
||||
Vagrant comes with many great features out of the box to get your environments
|
||||
up and running. Sometimes, however, you want to change the way Vagrant does
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Packaging and Distribution - Plugin Development
|
||||
sidebar_title: Packaging & Distribution
|
||||
description: |-
|
||||
This page documents how to organize the file structure of your plugin
|
||||
and distribute it so that it is installable using standard installation
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Custom Providers - Plugin Development
|
||||
sidebar_title: Providers
|
||||
description: |-
|
||||
This page documents how to add support for new providers to Vagrant, allowing
|
||||
Vagrant to run and manage machines powered by a system other than VirtualBox.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Custom Provisioners - Plugin Development
|
||||
sidebar_title: Provisioners
|
||||
script: |-
|
||||
This page documents how to add new provisioners to Vagrant, allowing Vagrant
|
||||
to automatically install software and configure software using a custom
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Plugin Usage - Plugins
|
||||
sidebar_title: Usage
|
||||
description: |-
|
||||
Installing a Vagrant plugin is easy, and should not take more than a few
|
||||
seconds.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Basic Usage - Providers
|
||||
sidebar_title: Basic Usage
|
||||
description: |-
|
||||
Vagrant boxes are all provider-specific. A box for VirtualBox is incompatible
|
||||
with the VMware Fusion provider, or any other provider. A box must be
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Configuration - Providers
|
||||
sidebar_title: Configuration
|
||||
description: |-
|
||||
While well-behaved Vagrant providers should work with any Vagrantfile with
|
||||
sane defaults, providers generally expose unique configuration options so that
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Custom Provider - Providers
|
||||
sidebar_title: Custom Provider
|
||||
description: |-
|
||||
To learn how to make your own custom Vagrant providers, read the Vagrant
|
||||
plugin development guide on creating custom providers.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Default Provider - Providers
|
||||
sidebar_title: Default Provider
|
||||
description: |-
|
||||
By default, VirtualBox is the default provider for Vagrant. VirtualBox is
|
||||
still the most accessible platform to use Vagrant: it is free, cross-platform,
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Basic Usage - Docker Provider
|
||||
sidebar_title: Basic Usage
|
||||
description: |-
|
||||
The Docker provider in Vagrant behaves just like any other provider.
|
||||
If you are familiar with Vagrant already, then using the Docker provider
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Boxes - Docker Provider
|
||||
sidebar_title: Boxes
|
||||
description: |-
|
||||
The Docker provider does not require a Vagrant box. The "config.vm.box"
|
||||
setting is completely optional.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Commands - Docker Provider
|
||||
sidebar_title: Commands
|
||||
description: |-
|
||||
The Docker provider exposes some additional Vagrant commands that are
|
||||
useful for interacting with Docker containers. This helps with your
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Configuration- Docker Provider
|
||||
sidebar_title: Configuration
|
||||
description: |-
|
||||
The Docker provider has some provider-specific configuration options
|
||||
you may set. A complete reference is shown on this page.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Docker Provider
|
||||
sidebar_title: Docker
|
||||
description: |-
|
||||
Vagrant comes with support out of the box for
|
||||
using Docker as a provider. This allows for your development environments
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Networking - Docker Provider
|
||||
sidebar_title: Networking
|
||||
description: |-
|
||||
The Vagrant Docker provider supports using the private network using the
|
||||
`docker network` commands.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Creating a Base Box - Hyper-V Provider
|
||||
sidebar_title: Creating a Base Box
|
||||
description: |-
|
||||
As with every Vagrant provider, the Vagrant Hyper-V provider has a custom box
|
||||
format that affects how base boxes are made.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Configuration- Hyper-V Provider
|
||||
sidebar_title: Configuration
|
||||
description: |-
|
||||
The Vagrant Hyper-V provider has some provider-specific configuration options
|
||||
you may set.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Hyper-V Provider
|
||||
sidebar_title: Hyper-V
|
||||
description: |-
|
||||
Vagrant comes with support out of the box for Hyper-V, a native hypervisor
|
||||
written by Microsoft. Hyper-V is available by default for almost all
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Limitations - Hyper-V Provider
|
||||
sidebar_title: Limitations
|
||||
description: |-
|
||||
The Hyper-V provider works in almost every way like the VirtualBox
|
||||
or VMware provider would, but has some limitations that are inherent to
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Usage - Hyper-V Provider
|
||||
sidebar_title: Usage
|
||||
description: |-
|
||||
The Hyper-V provider is used just like any other provider. Please read the
|
||||
general basic usage page for providers.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Providers
|
||||
sidebar_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.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Installation - Providers
|
||||
sidebar_title: Installation
|
||||
description: |-
|
||||
Providers are distributed as Vagrant plugins, and are therefore installed
|
||||
using standard plugin installation steps. After installing a plugin which
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Creating a Base Box - VirtualBox Provider
|
||||
sidebar_title: Creating a Base Box
|
||||
description: |-
|
||||
As with every Vagrant provider, the Vagrant VirtualBox provider has a custom
|
||||
box format that affects how base boxes are made.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Common Issues - VirtualBox Provider
|
||||
sidebar_title: Common Issues
|
||||
description: |-
|
||||
This page lists some common issues people run into with Vagrant and VirtualBox
|
||||
as well as solutions for those issues.
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue