-
-
Save epu/45c15be1a7f01d863b6c to your computer and use it in GitHub Desktop.
windows berks can't determine berks version
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| RuntimeError: Couldn't determine Berks version: #<Buff::ShellOut::Response:0x5fc39b8 @exitstatus=1, @stdout="", @stderr="C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/dependency.rb:296:in `to_specs': Could not find 'berkshelf' (>= 0) among 62 total gem(s) (Gem::LoadError)\n\tfrom C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/dependency.rb:307:in `to_spec'\n\tfrom C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/core_ext/kernel_gem.rb:47:in `gem'\n\tfrom C:/opscode/chefdk/embedded/bin/berks:22:in `<main>'\n"> |
This was with chefdk bin dirs in front of PATH. I don't have any ruby installed, nor rvm/rbenv on windows. This is just new out-of-the-box chefdk and plugins in vagrant.
PATH had a zombie chef-client path in it. User error.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Windows MSI Vagrant 1.6.2
vagrant-berkshelf (3.0.1)
vagrant-login (1.0.1, system)
vagrant-omnibus (1.4.1)
vagrant-share (1.0.1, system)