iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add additional detalis for Hyper-V users

This commit is contained in:
Esten Rye 2019-03-15 20:51:40 -05:00
parent 8f10683a20
commit 19c72f7867
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/source/docs/builders/vagrant.html.md
View File

@ -78,7 +78,17 @@ one, by using `global_id` instead of `source_box`.
vagrantfile. Our default template can be found vagrantfile. Our default template can be found
[here](https://github.com/hashicorp/packer/blob/a6d1d852bb0643e3593cc5d3dfe5ed80c4409b65/builder/vagrant/step_create_vagrantfile.go#L23-L30). So far the only template variables available to you are {{ .BoxName }} and [here](https://github.com/hashicorp/packer/blob/a6d1d852bb0643e3593cc5d3dfe5ed80c4409b65/builder/vagrant/step_create_vagrantfile.go#L23-L30). So far the only template variables available to you are {{ .BoxName }} and
{{ .SyncedFolder }}, which correspond to the Packer options `box_name` and {{ .SyncedFolder }}, which correspond to the Packer options `box_name` and
`synced_folder` `synced_folder`.
You must provide a template if your default vagrant provider is Hyper-V.
Below is a Hyper-V compatible template.
```ruby
Vagrant.configure("2") do |config|
config.vm.box = "{{ .BoxName }}"
config.vm.network 'public_network', bridge: 'Default Switch'
end
```
- `skip_add` (bool) - Don't call "vagrant add" to add the box to your local - `skip_add` (bool) - Don't call "vagrant add" to add the box to your local
environment; this is necessary if you want to launch a box that is already environment; this is necessary if you want to launch a box that is already