/lib64/libm.so.6: version 'GLIBC_2.27' not found in my self-hosted runners (Amazon Linux 2)

[kota65535]

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.

/opt/runner/externals/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /opt/runner/externals/node20/bin/node)
/opt/runner/externals/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /opt/runner/externals/node20/bin/node)

This is because:

• The action runtime is changed from node16 to node20 in the latest release v2.28.1 by this commit 587cee6
• Node.js v20.x requires glibc >= 2.28
• Amazon Linux 2 comes with glibc 2.26, so the action fails to run

It seems to be common to bump the major version if the action runtime is updated. For example:

• https://github.com/actions/checkout/releases/tag/v4.0.0
• https://github.com/actions/setup-go/releases/tag/v5.0.0

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.

[kota65535]

Oh, sorry duplicated #261

[dawidd6]

v2.28.1 tag was deleted, v2 now points to v2.28.0 as before.

v3.0.0 + v3 tags were created as per suggestion.

Thanks!

[kota65535]

@dawidd6 Thank you for the super-quick response!

[softok2]

Hello,
I have the same problem but at this date July 3,2024. Everything was working smoothly until today.
In my self-hosted runner I cannot upgrade node version I was using v3 tag, then switch to v2 without any improvement , so my question:
Is there any work around for sorting this issue?
Thanks in advance

[Idan-Lazar]

Hello, I have the same problem but at this date July 3,2024. Everything was working smoothly until today. In my self-hosted runner I cannot upgrade node version I was using v3 tag, then switch to v2 without any improvement , so my question: Is there any work around for sorting this issue? Thanks in advance

It happens to us too

[calopezf]

I have the same issue today July 3 2024. Please let us know how can we fix.

[adi-yuu]

+1
Facing this issue since July4 2024, is there a workaround for this ?

[anthonynguyen-tomo]

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.

[zhulinJulia24]

+1

[bohana]

+1, as of yesterday out self hosted runner was working fine.

[bing-scenius]

+1

[Idan-Lazar]

+1

[jprusakiewicz]

+1

[niQQe]

+1

[zhulinJulia24]

actions/checkout#1809 (comment)

it works for me

[dawidd6]

Nothing changed here in last 3 weeks, so I'm not sure if you should spam here about your issue.
GitHub forcefully updated node 16 to node 20, I see. Thanks @zhulinJulia24 for linking the relevant issue.

[jprusakiewicz]

There is workaround here:
actions/checkout#1590 (comment)

[joyyjoel]

Guys, I found a workaround, use this link or the comment below:

[mmomtchev](actions/checkout#1590 (comment))

env:
  ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true

in my workflow and it worked for me.

[ItayVortex]

@joyyjoel worked for me

[Vasanthan-Ponnivalavan]

env:
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true

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.

[dawidd6]

Please continue the discussion in relevant repository. Impacting change was made by GitHub, not by me. Thanks.