[chef] Re: Vagrant / Berkshelf /Chef Solo

[Zac Stevens < >]

Hi Rob,

Your tree output suggests that your cookbook is called "getting-started", while your Vagrant config refers to a cookbook called "starter".  You can see that in the Chef output:

[2013-11-25T14:55:59+00:00] INFO: Setting the run_list to ["recipe[starter]"] from JSON

Changing your chef.add_recipe to "getting-started" should do what you expect.

Zac

On Mon, Nov 25, 2013 at 3:34 PM, Rob Watkin < " target="_blank"> > wrote:

Chef solo cannot find my local cookbooks. I must be doing something stupid. Any help appreciated :-)

I have berkshelf setup ok with the following in my VagrantFile

config.vm.provision :chef_solo do |chef|

    chef.cookbooks_path = "cookbooks"

    chef.add_recipe "starter" 

end

$ tree cookbooks/getting-started/

cookbooks/getting-started/

├── README.rdoc

├── attributes

│   └── default.rb

├── metadata.json

├── metadata.rb

├── recipes

│   └── default.rb

└── templates

    └── default

        └── chef-getting-started.txt.erb

If I run $ vagrant up I get:

[2013-11-25T14:55:58+00:00] INFO: *** Chef 10.14.2 ***

[2013-11-25T14:55:59+00:00] INFO: Setting the run_list to ["recipe[starter]"] from JSON

[2013-11-25T14:55:59+00:00] INFO: Run List is [recipe[starter]]

<snip>

[2013-11-25T14:55:59+00:00] ERROR: Running exception handlers

[2013-11-25T14:55:59+00:00] ERROR: Exception handlers complete

[2013-11-25T14:55:59+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out

[2013-11-25T14:55:59+00:00] FATAL: Chef::Exceptions::CookbookNotFound: Cookbook starter not found. If you're loading starter from another cookbook, make sure you configure the dependency in your metadata

But if I run against a berkshelf cookbook e.g. (VagrantFile)

config.vm.provision :chef_solo do |chef|

    chef.cookbooks_path = "cookbooks"

    chef.add_recipe "apache2" 

end

my VM gets provioned ok

Thanks

Rob