update vagrant docs to explain that the builder and postprocessor are mutually exclusive
This commit is contained in:
parent
00ebf690c2
commit
5301f4613d
|
@ -30,6 +30,12 @@ by setting the `skip package` option. You can also change the behavior so that
|
|||
rather than initializing a new Vagrant workspace, you use an already defined
|
||||
one, by using `global_id` instead of `source_box`.
|
||||
|
||||
Please note that if you are using the Vagrant builder, then the Vagrant
|
||||
post-processor is unnecesary because the output of the Vagrant builder is
|
||||
already a Vagrant box; using that post-processor with the Vagrant builder will
|
||||
cause your build to fail. Similarly, since Vagrant boxes are already compressed,
|
||||
the Compress post-processor will not work with this builder.
|
||||
|
||||
## Configuration Reference
|
||||
### Required:
|
||||
|
||||
|
|
|
@ -45,6 +45,11 @@ providers.
|
|||
post-processor doesn't support creating boxes for a provider you care about,
|
||||
please help by contributing to Packer and adding support for it.
|
||||
|
||||
Please note that if you are using the Vagrant builder, then the Vagrant
|
||||
post-processor is unnecesary because the output of the Vagrant builder is
|
||||
already a Vagrant box; using this post-processor with the Vagrant builder will
|
||||
cause your build to fail.
|
||||
|
||||
## Configuration
|
||||
|
||||
The simplest way to use the post-processor is to just enable it. No
|
||||
|
|
Loading…
Reference in New Issue