haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

website/docs: mention require_vesrion

This commit is contained in:
Mitchell Hashimoto 2015-12-24 12:05:16 -08:00
parent 7d79cfd055
commit aba23205f7
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/docs/source/v2/virtualbox/configuration.html.md
View File

@ -44,7 +44,7 @@ and space (the new machine contains a copy of the base box's image).
Using linked clones can drastically reduce this overhead. Using linked clones can drastically reduce this overhead.
Linked clones are based on a master VM, which is generated by importing the Linked clones are based on a master VM, which is generated by importing the
base box only once the first time it is required. For the linked clones only base box only once the first time it is required. For the linked clones only
differencing disk images are created where the parent disk image belongs to differencing disk images are created where the parent disk image belongs to
the master VM. the master VM.
@ -62,6 +62,9 @@ config.vm.provider 'virtualbox' do |v|
end end
``` ```
If you don't want backward compatbility and want to force users to
support linked cloning, you can use `Vagrant.require_version` with 1.8.
<div class="alert alert-info"> <div class="alert alert-info">
<strong>Note:</strong> the generated master VMs are currently not removed <strong>Note:</strong> the generated master VMs are currently not removed
automatically by Vagrant. This has to be done manually. However, a master automatically by Vagrant. This has to be done manually. However, a master