Vagrant + Chef: Error in the provision "Public folders that require a chef are not on the virtual machine."

I installed Vagrant + Virtualbox using a chef (+ chef). When I do vagrant up for the first time, cookbooks load correctly. However, when I do this after this (be it vagrant provision , vagrant reload --provision or vagrant up --provision , I get this error:

 Shared folders that Chef requires are missing on the virtual machine. This is usually due to configuration changing after already booting the machine. The fix is to run a `vagrant reload` so that the proper shared folders will be prepared and mounted on the VM. 

I searched everywhere and the only solution was to do vagrant reload --provision , this worked before Vagrant 1.3.1.

+42
django vagrant virtualbox chef
Jan 16 '15 at 0:37
source share
2 answers

There seems to be an error with sync folders, this clears the cache and fixes it for me. (from the project directory)

 rm .vagrant/machines/default/virtualbox/synced_folders vagrant reload --provision 

https://github.com/mitchellh/vagrant/issues/5199

EDIT: this one should be fixed in vagrant 1.7.4

+106
Jan 26 '15 at 6:12
source share

This is a fairly common issue with branded plugins for Berkshelf and Librarian. Just get used to the execution of this command.

A way to avoid this is to use something like Test-Kitchen instead of Vagrant plugins. However, this is not a replacement.

-3
Jan 16
source share



All Articles