-
Notifications
You must be signed in to change notification settings - Fork 170
run as a normal user, chef gem install should install gems to a writable location #11
Comments
each bin wrappers have this code: ENV["GEM_HOME"] = ENV["GEM_PATH"] = nil unless ENV["APPBUNDLER_ALLOW_RVM"] == "true" so it may help to set |
and the above seems to be related to appbundler: https://github.com/opscode/appbundler#rvm |
Yeah, the binaries need to be rvm resistant, and |
We should consider writing gems to something like ➜ ls -la ~/.vagrant.d/gems/
total 0
drwxr-xr-x 8 schisamo staff 272 Mar 11 13:55 .
drwxr-xr-x 12 schisamo staff 408 Apr 22 14:06 ..
drwxr-xr-x 7 schisamo staff 238 Mar 17 06:39 build_info
drwxr-xr-x 7 schisamo staff 238 Mar 17 06:39 cache
drwxr-xr-x 2 schisamo staff 68 Mar 11 13:55 doc
drwxr-xr-x 7 schisamo staff 238 Mar 17 06:39 gems
drwxr-xr-x 3 schisamo staff 102 Mar 11 13:53 ruby
drwxr-xr-x 7 schisamo staff 238 Mar 17 06:39 specifications A |
@schisamo working on that right now |
Would it make sense to just use |
Merged a fix to omnibus-chef: chef-boneyard/omnibus-chef@af1f058 This will be fixed in the next chefdk release. |
@danielsdeleo - ❤️ |
This exactly happens again in version 0.8.0 on OSX El Capitan |
I occurred the same problem when use kitchen, it tries to write
My environment:
|
It would be nice if, as a normal user, I could install gems for Chef without requiring root access. This is of course supported by RubyGems itself, but apparently not with
chef gem
.Attempting to install a "Chef Gem" requires root access because it attempts to write to /opt.
Setting $GEM_HOME doesn't help, unfortunately.
My Chef Gem Environment:
The text was updated successfully, but these errors were encountered: