Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

GitHub actions workflow fails for self hosted runners #3972

Open
vishwas-agi opened this issue Jul 8, 2024 · 8 comments
Open

GitHub actions workflow fails for self hosted runners #3972

vishwas-agi opened this issue Jul 8, 2024 · 8 comments
Labels
question Further information is requested Stale

Comments

@vishwas-agi
Copy link

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
Copy link

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
Copy link
Member

npalm commented Jul 12, 2024

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

@vishwas-agi
Copy link
Author

vishwas-agi commented Jul 26, 2024

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
Copy link

use centos7.9 same

@vishwas-agi
Copy link
Author

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
Copy link

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?

@stuartp44 stuartp44 added the question Further information is requested label Jul 31, 2024
@npalm
Copy link
Member

npalm commented Aug 6, 2024

I would suggest to run on Ubuntu when possible, same as GItHub does. Alternative that works with most of the actions is amazon linux 2023.

Copy link
Contributor

github-actions bot commented Nov 5, 2024

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Nov 5, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
question Further information is requested Stale
Projects
None yet
Development

No branches or pull requests

4 participants