Bundle install with cached Ruby version fails , with writable permissions error . #633
Replies: 4 comments 2 replies
-
See #624 The permissions to have always been 777 (see actions/runner-images#10215 (comment)) so this seems an effect of a behavior change in Bundler. |
Beta Was this translation helpful? Give feedback.
-
Regarding the expected permissions, see #624 (comment). |
Beta Was this translation helpful? Give feedback.
-
Hi @eregon , could you provide the link to the Bundler tracker , it would be helpful for me in finding the right channel. thanks |
Beta Was this translation helpful? Give feedback.
-
thanks @eregon |
Beta Was this translation helpful? Give feedback.
-
Hi team, we do have customer issue .
Error:
The installation path is insecure. Bundler cannot continue."/opt/hostedtoolcache/Ruby/3.2.4/x64/lib/ruby/gems/3.2.0/gems" is world-writable(without sticky bit).Bundler cannot safely replace gems in world-writeable directories due to potential vulnerabilities.Please change the permissions of this directory or choose a different install path.
Analysis:
This new behaviour seems to be the result of bundler v2.5.12 release, from this PR in particular.
rwxrwxrwx
rights we have explicitly configured for /opt directory.We need your guidance in fixing permissions during the image generation in our Ruby , and what might the implication if we use chmod -R o-w for Ruby folder.`
Beta Was this translation helpful? Give feedback.
All reactions