.├── Berksfile├── Berksfile.lock├── Gemfile├── Gemfile.lock├── README.md├── Thorfile├── Vagrantfile├── attributes├── aws.rb├── berks-cookbooks├── boothook.sh├── chefignore├── cloud-config.yaml├── combined.txt├── cookbooks├── data_bags├── definitions├── environments├── files├── get_aws_creds.rb├── littlechef.cfg├── local-machines.rb├── metadata.rb├── nodes├── recipes├── roles├── site-cookbooks├── test├── user_data.yaml├── write-mime-multipart└── write-sudoer-requiretty.yaml
[userinfo]user = ec2-userpassword =keypair-file = /Users/xxx/.ssh/ec2-us-west-2.pemssh-config = /Users/xxx/.ssh/configencrypted_data_bag_secret =[kitchen]node_work_path = /tmp/chef-solo/berksfile = Berksfileberksfile_cookbooks_directory = cookbooks
You should not need to run berks vendor manually. Can you share screen log with me from littlechef run with debug flag enabled and with/without berk_cookbook_directory in your config.
Another question is what version of littlechef do you use and from which repository ?
Frankly I'm not sure where the problem was.
zsh 4847 (git)-[master]-% fix -V node:jenkins-masterVerbose output onFatal error: Couldn't find cookbooks. Are you executing 'fix' outside of a kitchen?To create a new kitchen in the current directory type 'fix new_kitchen'Aborting.