vagrant berks issue with ChefDK 12.7.2

gistfile1.txt

Stevens-MacBook-Pro:bamboo-agent-cookbook stevenwade$ vagrant plugin install vagrant-berkshelf
Installing the 'vagrant-berkshelf' plugin. This can take a few minutes...
Installed the plugin 'vagrant-berkshelf (4.1.0)'!
Post install message from the 'vagrant-berkshelf' plugin:

The Vagrant Berkshelf plugin requires Berkshelf from the Chef Development Kit.
You can download the latest version of the Chef Development Kit from:

    https://downloads.chef.io/chef-dk/

Installing Berkshelf via other methods is not officially supported.

Stevens-MacBook-Pro:bamboo-agent-cookbook stevenwade$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
The following berks command failed to execute:

    /opt/chefdk/embedded/bin/berks --version --format json

The stdout and stderr are shown below:

    stdout:
    stderr: /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems.rb:241:in `bin_path': can't find gem berkshelf (>= 0.a) (Gem::GemNotFoundException)
	from /opt/chefdk/embedded/bin/berks:22:in `<main>'

Stevens-MacBook-Pro:bamboo-agent-cookbook stevenwade$ knife -v
Chef: 12.7.2
Stevens-MacBook-Pro:bamboo-agent-cookbook stevenwade$

There's a difference between Chef-client (12.7.2) and Chef-DK (current version 11.2). On workstations, chef-client does not need to be installed, you can get everything from Chef-DK.

Hopefully this helps: https://downloads.chef.io/chef-dk/mac/

Did you end up figuring out how to resolve this? I have Chef-DK v11.2.x installed and I get the exact same error:

`ben.dry@alig1511 jurlique-ngp]$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
The following berks command failed to execute:

/opt/chefdk/embedded/bin/berks --version --format json

The stdout and stderr are shown below:

stdout: 
stderr: /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems.rb:241:in `bin_path': can't find gem berkshelf (>= 0.a) (Gem::GemNotFoundException)
from /opt/chefdk/embedded/bin/berks:22:in `<main>'

`

@captainbenno Can you run chef -v and post your output?

I'm having the same issue. Output is:

$ chef -v
Chef Development Kit Version: 0.14.25
chef-client version: 12.10.24
berks version: 4.3.5
kitchen version: 1.8.0