Closed mzupan closed 9 years ago
so I just tried v2.0.1 and it works but it doesn't upload any community plugins.. only the local ones
doesn't upload any community plugins
I'm not sure what this means.
This is probably a bug in 4.0.0 since it was a large refactor.
so i figured it out.. and it seems due to multi node vagrant file
When I do a berks install
it installs all the cookbooks and in ~/.berkself/cookbooks but the plugin is looking for them in ~/.berkself/web/cookbooks which is empty
If I create a symlink it works
The plugin should be looking in ~/.berkshelf/vagrant-berkshelf/<randomstring>/
... I'm not really sure what you are saying here
I don't even have a ~/.berkshelf/vagrant-berkshelf/ created when i run a vagrant up. If i ran
ln -s ~/.berkshelf/cookbooks ~/.berkshelf/web/
Things worked with v2.0.1
@mzupan I'm not sure what version of Vagrant Berkshelf you're using, but that's actually not possible unless you are overriding ENV["BERKSHELF_PATH"]
: https://github.com/berkshelf/vagrant-berkshelf/blob/79daaf237a48c36a936d0ad46e52b82d71435947/lib/vagrant-berkshelf.rb#L9-15.
Berkshelf will install cookbooks into ~/.berkshelf
(since that's what Berkshelf does), and then Vagrant Berkshelf uses ~/.berkshelf/vagrant-berkshelf/shelves
to store the vendored directories.
maybe its a https://github.com/andrewgross/vagrant-chef-zero issue then
@mzupan I'm not familiar with that plugin. Vagrant 1.7 will have native support for Chef Zero and this plugin is written to accommodate that when released. Can you try using Chef Solo and see if the issue persists? At least we can narrow it down.
@sethvargo thanks.. chef-solo worked.. must be the other plugin.. sorry for the confusion and thanks for the help
@mzupan no problem. When Vagrant 1.7 is released, you won't need the other plugin
I have the following vagrant file
on a
vagrant up web
i'm getting an errorplugins are as follows
Vagrant version