Context
I am setting up CI on GitHub Actions, which was recently connected to an Amazon Linux 2 instance. I suspect the problems are to do with permissions when ruby-setup tries to make new folders on the instance, but the stack trace is vague. This happens in two distinct jobs that both require ruby.
Stacktrace
Run ruby/setup-ruby@v1
with:
ruby-version: default
bundler: default
bundler-cache: false
working-directory: .
cache-version: 0
env:
ImageOS: ubuntu20
JAVA_HOME_8_x64: /home/ec2-user/actions-runner/_work/_tool/jdk/8.0.292/x64
JAVA_HOME: /home/ec2-user/actions-runner/_work/_tool/jdk/8.0.292/x64
JAVA_HOME_8_X64: /home/ec2-user/actions-runner/_work/_tool/jdk/8.0.292/x64
Using ruby-2.3.1 as input from file .ruby-version
Error: ENOENT: no such file or directory, mkdir
and
Run ruby/setup-ruby@v1
with:
ruby-version: default
bundler: default
bundler-cache: false
working-directory: .
cache-version: 0
env:
PGHOST: localhost
PGUSER: postgres
RAILS_ENV: test
ImageOS: ubuntu20
Using ruby-2.3.1 as input from file .ruby-version
Error: ENOENT: no such file or directory, mkdir
Before setup-ruby, checkout runs successfully for both steps.
setup-ruby
https://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby
Troubleshooting
I have tried:
- Modifying permissions for the user (
ec2-user) - Looking for alternative Actions, this appears to be the only one maintained
What do I need to do so that these steps can complete?