Closed mikedep333 closed 9 years ago
I'm reopening this because I am experiencing the issue again and I do not know why. I did switch from my duckduckhack-vm branch to the master branch. I think it is related to the Gemfile.lock file.
I figured out that vagrant plugin install
(typically) ignores the system gems and installs gems to ~/.vagrant.d/gems/
. It seems to set both GEM_HOME
and GEM_PATH
to that path.
In conclusion, I am getting closer to a fix.
@mikedep333 I just made it work. Here is the step I've done.
vagrant install vagrant-berkshelf
ChefDK
and run the command below to add Chef's bin to PATHecho 'eval "$(chef shell-init SHELL_NAME)"' >> ~/.YOUR_SHELL_RC_FILE
Hi @heytitle
I figured that would fix the problem. However, I am hoping to avoid having to tell people to install the ChefDK, which is supposed to be installed from an installer/package on their website and is not available for every single Linux distro.
I'll discuss this on the mailing lists. -Mike
@mikedep333
Maybe you want to change line 57 in $HOME/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.1/lib/berkshelf/vagrant/config.rb
?
@client_key = File.expand_path(@client_key.to_s, machine.env.root_path.to_s)
A user reported this issue: http://www.listbox.com/member/archive/197814/2014/12/sort/time_rev/page/1/entry/3:7/20141216115156:D6203160-8543-11E4-9E01-82B128BEBCD2/
Upon further investigation, this is a bug in ridley, a dependency of berkshelf (and therefore vagrant-berkshelf): https://github.com/RiotGames/ridley/issues/285