I had thought of that. One problem is that `vagrant package` took about 15 minutes to complete.
The other problem is that I'm unclear how I can 'restore' the results of `vagrant package`. My understanding of said command is that it prepares your box to be distributed, not be reused locally. Do you know how I could accomplish the later? On Wednesday, March 23, 2016 at 9:47:16 AM UTC-4, Alvaro Miranda Aguilera wrote: > > Hello, > > Vagrant uses Virtualbox uuid to identify boxes. > > VBoxManage list vms > > So, if you destroy, then will be some manual work. > > I think the easiest way is to do a vagrant package , just be sure to > delete /etc/udev/rules.d/70-persistent-net.rule or similar file, then > shutdown. > > > Alvaro. > > > On Thu, Mar 24, 2016 at 2:15 AM, Tim Visher <[email protected] > <javascript:>> wrote: > >> Hi Everyone, >> >> We have a very lengthy and sadly brittle provisioning process. Making >> both of those better is on our roadmap but it unfortunately makes people >> very nervous about recreating their VMs which leads to other problems. >> >> I had the idea that I could make a backup of the box prior to destroying >> it, then if anything goes wrong with the provision, you can always fall >> back to the backup. >> >> I don't believe snapshotting can work here because we want to be able to >> destroy the box and then recreate it (maybe that's problem number 1?). >> >> My initial idea was to do a `VBoxManage clonevm` step prior to destroying >> the box and then if anything goes wrong clone the vm back into place and >> allow you to continue on your way. >> >> My first attempt at this did not go well though, and I'm unclear as to >> why. Vagrant recognized the machine as already provisioned, but the box >> itself definitely was not provisioned. >> >> How can I do this? Or is there a better way to accomplish what I'm >> talking about. >> >> Thanks in advance! >> >> -- >> >> In Christ, >> >> Timmy V. >> >> http://blog.twonegatives.com/ >> http://five.sentenc.es/ -- Spend less time on mail >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/c2f79ca4-8b29-4037-b035-6fd78301a73c%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/c2f79ca4-8b29-4037-b035-6fd78301a73c%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/579b7d03-b471-4e68-a220-bf2de1f19bea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
