-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gem conflict on Windows workstation, not sure how to solve #20
Comments
Yeah. These Gem conflicts can be truly painful. Usually the first thing you can try is just blow away your Gemfile.lock file and do a fresh bundle install. That will force bundler to resolve everything fresh and it may result in a conflict free bundle. |
I am getting this same error after upgrading test-kitchen from 1.11.0 to 1.13.0. hmm |
might try installing the latest chef-dk (0.18.26) to clear up any gem conflicts |
Similar issue happened to me. I used
Maybe I'm mistaken, but thought chef-dk includes kitchen by default, and kitchen uses the gems bundled with chef-dk ... When I dug into it a bit, found this in the
Wasn't sure if 1.10.2 or 1.13.2 was the version that came with chef-dk and how two ended up conflicting. I suspect kitchen-nodes causes 1.13.2 to be pulled in? But it's not really there at all?
Checking for update
And I can confirm I'm running the latest "stable" chefdk for Ubuntu 16.04 LTS
But it looks quite a bit behind
|
See #29 for more info and hints tl;dr = use |
This isn't necessarily an issue with
kitchen-nodes
but the guy on my team exhibiting this issue can install and use chef-zero just fine, and I wouldn't expect the gem dependencies in question to be different.Disclaimer: my ruby experience is entirely based in Chef. This could turn out to be a painfully n00b-ish issue.
After doing a
gem install kitchen-nodes
(we try not to use bundler with Chef/test-kitchen) and then issuing a kitchen command:and then the relevant section of
.kitchen.log
:I'm the only other one on our team testing with kitchen-nodes at the moment, and I have no issue but I'm also using a Mac.
Is there something we should explicitly install to resolve this, or is kitchen-nodes just not compatible with the Chef 12.4.3 gem on Windows?
The text was updated successfully, but these errors were encountered: