-
Notifications
You must be signed in to change notification settings - Fork 213
knife cook should (?) force omnibus ruby if available #140
Comments
That could be tricky since rvm also mucks with the path. Perhaps we could manipulate the path on a |
If you have a set of recipes or AMI that reproduce the situation, definitely post it btw. I don't typically use rvm in production. |
This issue on the chef-rvm repo may help: sous-chefs/rvm#125. |
Thinking about this a bit more. If you run 'which chef-solo' what do you get? Do you have a copy of the chef gem under rvm as well? I would expect that the omnibus copy of chef-solo has a hardcoded path to the embedded ruby. |
If I cook a second time I get this error:
|
Hey all, I've merged sous-chefs/rvm#125 into master. @hrp It looks to me like RVM might be loaded (login shell perhaps?) and it's trying to use your default RVM Ruby's RubyGems. When I get this logged into a box I can usually clear it with an |
@matschaffer Sure, go ahead and close this. I haven't seen this problem lately (I've been using a fork of chef-rvm with the above commit included) so it may be solved. If I notice it again, I'll try @fnichol's solution. If that doesn't work out, I can reopen or make a new issue. |
Thanks @hrp! |
FWIW I had the same issue and "rvm system" resolved it for me. |
Right now if sudo has acces to rvm it will use the rvm default ruby rather than the omnibus ruby. Any ideas how to work aroudn this?
The text was updated successfully, but these errors were encountered: