-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Base box documentation needs update to include vagrant package
command
#47
Comments
mguterl, The
Thanks for the suggestion, |
mguterl, You'll be happy to hear that base boxes can now be packaged with The documentation (in the docs branch) will be updated shortly, but in short: This change simplifies base box creation quite a bit. It completely removes the step requiring base box creators to "copy down the MAC address" since Vagrant now automates this. Mitchell |
mguterl, Here is an example, by the way, of how this works: Say you create a base box and its named "karmic" within VirtualBox. After you get ruby/chef/whatever-you-want setup on the base box, you can now package it up into a box by going into any directory and typing the following:
You can still include your own custom Vagrantfiles in the base box packages as well (to forward ports or whatever you wish):
Simple! |
Currently the documentation at http://vagrantup.com/docs/base_boxes.html gives you instructions for packaging a new base box by using tar by hand.
http://vagrantup.com/docs/boxes.html briefly mentions creating boxes and shows using the
vagrant package
command. I think the base_boxes.html page should be updated to reflect the use of this command rather than manual tarring.The text was updated successfully, but these errors were encountered: