bundle install fails within a ruby devcontainer due to permissions issues

[AlexChesser]

I expect that I'm actually doing this wrong, but I'm trying to launch a devcontainer and am hitting a wall here.

The following dockerfile builds fine

ARG RUBY_VERSION=3.2
ARG BUNDLE_RUBYGEMS__PKG__GITHUB__COM
ARG BUNDLE_ENTERPRISE__CONTRIBSYS__COM
ARG ROLLBAR_WRITE_TOKEN
ARG CIRCLECI_TOKEN
ARG SORBET_VERSION=0.5.11054
FROM alexchesser/sorbet-linux-aarch64-binaries:${SORBET_VERSION} as sorbet-binaries
FROM mcr.microsoft.com/vscode/devcontainers/ruby:${RUBY_VERSION}  as base
RUN chown vscode -hR /usr/local/rvm /usr/local/bin/gem /usr/local/lib/ruby
COPY --from=sorbet-binaries '/dist' '/sorbet-binaries'
RUN gem install --source file:///sorbet-binaries sorbet:0.5.11054

if I try to log in as the vscode user and run something like "gem install rails" I get a permissions error

su vscode
gem install rails
[... a lot of text ... ]
ERROR:  While executing gem ... (Gem::FilePermissionError)
    You don't have write permissions for the /usr/local/rvm/gems/default directory.
	/usr/local/lib/ruby/3.2.0/rubygems/installer.rb:712:in `verify_gem_home'

Is there some sort of "magic" end users have to do to ensure their vscode user has permissions to execute development commands?

[samruddhikhandale]

Hi 👋

Can you try adding 👇 at the end of your Dockerfile?

RUN su vscode -c "/usr/local/rvm/bin/rvm fix-permissions"

Then, you should be able to install gems with su vscode -c "gem install <your-gem-names-here>"

[AlexChesser]

oh yay! thanks so much that fixed it. I could even remove that ugly line:

RUN chown vscode -hR /usr/local/rvm /usr/local/bin/gem /usr/local/lib/ruby