That worked. Thanks. This seems like a pretty major Vagrant bug. On Tuesday, May 12, 2015 at 4:34:29 PM UTC-5, Torben Knerr wrote: > > Hi Jeff, > > you might be running into this: > https <https://github.com/mitchellh/vagrant/issues/5199>:// > <https://github.com/mitchellh/vagrant/issues/5199>github.com > <https://github.com/mitchellh/vagrant/issues/5199>/mitchellh/vagrant/ > <https://github.com/mitchellh/vagrant/issues/5199>issues > <https://github.com/mitchellh/vagrant/issues/5199>/5199 > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues%2F5199&sa=D&sntz=1&usg=AFQjCNHRP-hzI2Jt0TGUiqrYZkYYjpv_yA> > > Workaround: > > `rm .vagrant/machines/default/virtualbox/synced_folders` before `vagrant > reload` > > HTH, Torben > Have a Vagrantfile with a chef-solo provisioner and a few cookbooks. > 'vagrant up' and 'vagrant provision' work fine. However, after 'vagrant > reload' the cookbooks appear to have been deleted from the guest. On a > Centos guest, /tmp/vagrant-chef/.../cookbooks directory on the guest is > empty. On an Ubuntu guest, /tmp/vagrant-chef is empty. In either case > provisioning fails. Have never seen this behavior before. Running Vagrant > 1.72/VirtualBox 4.3/OSX Yosemite. > > -- > 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 vagrant-up+...@googlegroups.com <javascript:>. > For more options, visit https://groups.google.com/d/optout. >
-- 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 vagrant-up+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
