Hashie Error in ChefDK 1.2.22 #1157
Comments
It's an issue that Berkshelf pulls in - berkshelf/berkshelf#1668 |
Duplicate of #1155 |
Work around until Berks 5.6.1 is part of ChefDK. |
closing as dup |
- Add Travis CI Build Status Icon - Add .ruby-version file (2.2) - Add cross-platform user-detection for Travis CI testing in Linux - Work around for a berkshelf-related issue: chef-boneyard/chef-dk#1157
- Add Travis CI Build Status Icon - Add .ruby-version file (2.2) - Add cross-platform user-detection for Travis CI testing in Linux - Work around for a berkshelf-related issue: chef-boneyard/chef-dk#1157
@damacus I just tried running |
@fernandoaleman the problem is when you run If you run a I work around the above by setting the following in my
This will ensure that anytime I run a gem binary it will first use the ones installed via chefdk (NOTE: this may not be something you always want - so be aware) |
@sarkis Thank you very much for the help. That worked perfectly. 👍 |
@fernandoaleman the only catch with my solution is that later versions of chefdk will likely use a different ruby version - so I have to from time to time go in and change I just changed my PATH to use |
@sarkis 's solution wasn't working for me. I kept getting errors reading Here's an alternative solution that worked for me, in case anyone runs into the same problem:
That should completely replace 5.6.0 Berkshelf with 5.6.4 in your /opt/chef/ directory. |
yea, I'm still having this problem with chefdk -
|
Description
Hashie Error in ChefDK 1.2.22
See Travis jobs run since ChefDK 1.2.22 came out.
https://travis-ci.org/sous-chefs/samba/jobs/198444465
https://travis-ci.org/sous-chefs/haproxy/jobs/198174545
I get the same errors running from my laptop.
Update:
I've updated my local machine to use 1.3.6, and the error is still occurring
ChefDK Version
1.2.22
Platform Version
OSX 10.12.3
Travis
Replication Case
Install chefdk 1.2.22 and run a
kitchen
commandThe text was updated successfully, but these errors were encountered: