p to main contentDocumentationInstallationCommands (CLI)Vagrant ShareVagrantfileBoxesProvisioningNetworkingSynced Folder
251 results for "vagrant"
-
Disks for VirtualBox Provider | Vagrant | HashiCorp Developer
-
Basic Usage - Provisioning | Vagrant | HashiCorp Developer
rs are run in three cases: the initial vagrant up, vagrant provision, and vagrant reload --provision.A --no-provision flag -
Configuration- Docker Provider | Vagrant | HashiCorp Developer
SIGTERM to the process.vagrant_machine (string) - The name of the Vagrant machine in the vagrant_vagrantfile to use as the -
Commands - Docker Provider | Vagrant | HashiCorp Developer
image. However, the associated Vagrant command to docker-exec into this instance is:$ vagrant docker-exec -it -- /bin/sh CopyIn -
Default Provider - Providers | Vagrant | HashiCorp Developer
the default provider for Vagrant. VirtualBox is still the most accessible platform to use Vagrant: it is free, cross-platform -
config.vm - Vagrantfile | Vagrant | HashiCorp Developer
If true, Vagrant will check for updates to the configured box on every vagrant up. If an update is found, Vagrant will tell -
Custom Hosts - Plugin Development | Vagrant | HashiCorp Developer
page documents how to add new host OS detection to Vagrant, allowing Vagrant to properly execute host-specific operations on -
Custom Provisioners - Plugin Development | Vagrant | HashiCorp Developer
ProvisionersThis page documents how to add new provisioners to Vagrant, allowing Vagrant to automatically install software and configure -
Vagrant Post-Processor | Integrations | Packer | HashiCorp Developer
agoGitHub(opens in new tab)Vagrant CloudType: vagrant-cloud Artifact BuilderId: pearkes.post-processor.vagrant-cloudVagrant Cloud -
Host Capabilities - Plugin Development | Vagrant | HashiCorp Developer
the core of Vagrant. In earlier versions of Vagrant, all the host logic was contained in the core of Vagrant and was not