Closed joegoggins closed 10 years ago
@joegoggins how did you install chefdk? Also what's your core ruby install? There's a few variables that can help troubleshoot this. Also what OS are you on?
"how did you install chefdk?"
I installed it through https://downloads.getchef.com/chef-dk/mac/#/ and selected 0.2.1.
"what's your core ruby install?"
Normally I use chruby + 1.9.3. But I disabled all of that first and used the instructions here: https://github.com/opscode/chef-dk#using-chefdk-as-your-primary-development-environment
It looks like the gemspec on knife-container is pinned to chef 11 here whereas chef-dk is pinned to 12 here ...
@joegoggins nice catch, I think we have a pinning issue. @tduffield can you confirm?
This is an issue. I was unaware that chef-dk had bumped to chef 12 alpha. I'll get a quick fix out today that will address the issue.
knife-container v0.2.2 has been released to rubygems. It should now support chef12.
Cool, thanks for the rapid turnaround on this. There is so much awesome container tooling coming out like this. I also appreciate that you spell out the 1.0.0 vision in the changelog too, helps me stay stoked and tuned in.
Hi there,
It looks like the knife-container has chef 11.x pinned in the gemspec, whereas the chef-dk requires chef 12.alpha pinned and thus I get a
Unable to activate knife-container-0.2.1, because chef-12.0.0.alpha.1 conflicts with chef (~> 11.0)
I suppose I'll downgrade chef-dk to 0.2.0 so it'll work again... or perhaps I'm doing something wrong. Here's what I did: