ruby_install definition breaking on El Capitan

[mjstallard]

Hello!

We're just trying to use sprout wrap on a clean build of El Capitan, and we're seeing a strange issue. During the sprout_base_bash_it_enable_feature action, we get a failure due to the ruby_install definition in sprout-rbenv being unable to complete as it cannot write to the /Library/Ruby/Gems/2.0.0 directory.

We can do a temporary workaround by issuing:

sudo chown -R pivotal:staff /Library/Ruby

...but that feels wrong to us.

Please find below the output of running soloist:

soloist_output.txt
ruby-build_output.txt

We are using the latest Pivotal machine image, which appears to be a pretty bare-bones El Capitan 10.11.4. System Integrity Protection is enabled.

Thanks! 😄

Mike and Heather

[wendorf]

Hi @mjstallard ,

Looking at the output, rubygems for Ruby 2.2.3 believes that your gem_home is the Ruby 2.0.0 gem home. The logic for finding the gem_home is here (possibly an older commit, though). A sudo will get you past the error, but doesn't fix the underlying problem, since your 2.2.3 Ruby won't have its default gems installed.

It would be really helpful if you could look at the gem_home logic and compare it to your system state to see why it's getting the system Ruby location instead of the newly-installed Ruby. Possibly due to overriding environment variables?

My suspicion is that rbenv is not playing nicely with getting called from within a bundle exec of soloist. The bundle exec may be setting environment variables that rbenv is not sufficiently overriding.

If you're having trouble tracking down the exact issue, another interesting experiment would be to install the same rubies using pivotal-sprout/sprout-chruby. That would at least narrow down the cause.

[mjstallard]

Update - so we switched out the references to sprout-rbenv and rbenv from the soloistrc, and replaced them with sprout-chruby and everything worked just fine from a clean install.

[wendorf]

This feels like an issue that may be fixed by improvements to sprout-base's PATH manipulation. Worth investigating.