-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/lib64/libm.so.6: version 'GLIBC_2.27' not found
in my self-hosted runners (Amazon Linux 2)
#262
Comments
/lib64/libm.so.6: version
GLIBC_2.27' not found` in my self-hosted runners (ex: Amazon Linux 2)/lib64/libm.so.6: version 'GLIBC_2.27' not found
in my self-hosted runners (ex: Amazon Linux 2)
/lib64/libm.so.6: version 'GLIBC_2.27' not found
in my self-hosted runners (ex: Amazon Linux 2)/lib64/libm.so.6: version 'GLIBC_2.27' not found
in my self-hosted runners (Amazon Linux 2)
Oh, sorry duplicated #261 |
Thanks! |
@dawidd6 Thank you for the super-quick response! |
Hello, |
It happens to us too |
I have the same issue today July 3 2024. Please let us know how can we fix. |
+1 |
One solution is to upgrade ami images to AL2023 as it has the higher version of glibc that node is compatible with. See https://docs.aws.amazon.com/linux/al2023/ug/glibc-gcc-and-binutils.html. |
+1 |
+1, as of yesterday out self hosted runner was working fine. |
+1 |
3 similar comments
+1 |
+1 |
+1 |
actions/checkout#1809 (comment) it works for me |
Nothing changed here in last 3 weeks, so I'm not sure if you should spam here about your issue. |
There is workaround here: |
Guys, I found a workaround, use this link or the comment below: [mmomtchev](actions/checkout#1590 (comment))
in my workflow and it worked for me. |
@joyyjoel worked for me |
env: This doesn't work for me, actually it passes during the checkout phase and the build fails due to timeout error after this command was ran, I tried to change versions from v:11.3-alpine to v:14 -alpine and changed gitcheckout from v3 to v4 and downgraded to v2 and v1 as well, these solution doesn't work for me from july 4,2024 I'm facing this issue. |
Please continue the discussion in relevant repository. Impacting change was made by GitHub, not by me. Thanks. |
Hi @dawidd6. First of all, thanks for creating and maintaining this useful action.
We are using this action in our Amazon Linux 2 self-hosted runners. Recently, we've hit the following error message.
This is because:
node16
tonode20
in the latest release v2.28.1 by this commit 587cee6It seems to be common to bump the major version if the action runtime is updated. For example:
It would be helpful if you could change the latest release tag to v3.0.0 and v3, and revert the v2 tag to refer v2.28.0 again.
The text was updated successfully, but these errors were encountered: