-
Notifications
You must be signed in to change notification settings - Fork 168
Comments
workaround: |
Why are you running with |
Because my user had no privilege to write to /var/lib/ruby The problem exhibited itself the same with a non sudo execution with |
@webmonkey you shouldn't need sudo to run ChefDK - that's one of the purposes. You should just run... You are using the system ruby at that point, which is why you have permission issues. |
@sethvargo we're gonna have to work out something with kitchen to make it either skip the driver install or use a custom command instead of |
Thanks Seth, I'm very much a newcomer to this. Following an uninstall of the gem I'm still able to replicate the issue.
|
Well, that definitely seems like a bug... @danielsdeleo I was able to reproduce. I don't think I should need to use
|
@sethvargo right, see #11 for the gem permissions issue. The second problem is that ChefDK's |
I had already run
sudo chef gem install kitchen-vagrant
and have seen #15 which could be related.edit: I'm using Ubuntu 12.04 if that's at all relevant
At first it looked to be using the default OS installed
gem
commandI modified the path to force the chefdk packaged
gem
It still errors but I don't figure why it's trying to re-install when the package is installed already.
The text was updated successfully, but these errors were encountered: