search

philips-labs / terraform-aws-github-runner

Terraform module for scalable GitHub action runners on AWS
https://philips-labs.github.io/terraform-aws-github-runner/
MIT License
2.47k stars 588 forks source link

GitHub actions workflow fails for self hosted runners #3972

Open vishwas-agi opened 3 weeks ago

vishwas-agi commented 3 weeks ago

Hi Team,

We have setup the dynamic self hosted runners from the instructions in this repository and it was working fine all these days, but we are having a strange issue from 3 days with our self hosted runners workflow fails at the checkout step.

Error we are facing /opt/actions-runner/externals/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/actions-runner/externals/node20/bin/node) image

If you could suggest on this please.

Regards,

sandiandian commented 3 weeks ago

It should be due to Github upgrading the node version of actions to 20 https://github.blog/changelog/label/actions/ At present, this problem can be solved by adding environment variables. ACTIONS ALLOW-USE-UNSECURE NODE VERSION=true, but there may still be problems after October. Is there any way to keep using node16

npalm commented 2 weeks ago

All examples in examples/multi-runner are working. What base image are you using?

vishwas-agi commented 5 days ago

All examples in examples/multi-runner are working. What base image are you using?

Amazon Linux 2 OS we had used in the dynamic runner setup.

sandiandian commented 5 days ago

use centos7.9 same

vishwas-agi commented 5 days ago

use centos7.9 same What needs to be changed in the terraform or lambdas, any idea on that ?

It should be due to Github upgrading the node version of actions to 20 https://github.blog/changelog/label/actions/ At present, this problem can be solved by adding environment variables. ACTIONS ALLOW-USE-UNSECURE NODE VERSION=true, but there may still be problems after October. Is there any way to keep using node16

Also you had mentioned temporary workaround, did you get it working ?

sandiandian commented 5 days ago

use centos7.9 same What needs to be changed in the terraform or lambdas, any idea on that ?

It should be due to Github upgrading the node version of actions to 20 https://github.blog/changelog/label/actions/ At present, this problem can be solved by adding environment variables. ACTIONS ALLOW-USE-UNSECURE NODE VERSION=true, but there may still be problems after October. Is there any way to keep using node16

Also you had mentioned temporary workaround, did you get it working ?

Yes, but is there a long-term solution?