You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running on rhel7 with self-hosted runners and starting today we're running into issues where @V3 is using node20 instead of node16.
Happening on runner versions 2.316.1 and 2.317.0.
Oddly some of our Repos don't run into this issue when executing checkout@v3 on the same runners.
Run actions/checkout@v3
/ci_storage_agent_1/actions-runner/externals/node20/bin/node: /lib64/libm.so.6: version GLIBC_2.27' not found (required by /ci_storage_agent_1/actions-runner/externals/node20/bin/node) /ci_storage_agent_1/actions-runner/externals/node20/bin/node: /lib64/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /ci_storage_agent_1/actions-runner/externals/node20/bin/node)
/ci_storage_agent_1/actions-runner/externals/node20/bin/node: /lib64/libstdc++.so.6: version CXXABI_1.3.9' not found (required by /ci_storage_agent_1/actions-runner/externals/node20/bin/node) /ci_storage_agent_1/actions-runner/externals/node20/bin/node: /lib64/libstdc++.so.6: version GLIBCXX_3.4.21' not found (required by /ci_storage_agent_1/actions-runner/externals/node20/bin/node)
/ci_storage_agent_1/actions-runner/externals/node20/bin/node: /lib64/libc.so.6: version GLIBC_2.28' not found (required by /ci_storage_agent_1/actions-runner/externals/node20/bin/node) /ci_storage_agent_1/actions-runner/externals/node20/bin/node: /lib64/libc.so.6: version GLIBC_2.25' not found (required by /ci_storage_agent_1/actions-runner/externals/node20/bin/node)
Reacted by Chris Turner, Jonathan Morarity, Adrian Palacios, Jesse Cooke, Jasper Lin, Victor Hugo Batista, christophersavory, biswalc, Judy Li, kakepi0326 and 71 more
Reacted by 조중현, shogo, Dmytro Sirenko, William Cowen, Cristian Paul Peñaranda Rojas, Jakub Beránek, fumi hata, Bjorge Meulemeester, Shockingly Good and Noe
Hello! Our development team is also experiencing the same issue. We are using AWS instances as self-hosted.
We temporarily resolved the issue by simply changing the node16 directory to node20 in the same path. 🥲
/home/ec2-user/actions-runner/externals/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /home/ec2-user/actions-runner/externals/node20/bin/node)
/home/ec2-user/actions-runner/externals/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /home/ec2-user/actions-runner/externals/node20/bin/node)
I tried setting this inside a workflow running on GH hosted runners and it didn't work.
So it looks like this only works when the runner itself was started with those set, i.e. you cannot set them for a running runner which includes the GH hosted ones.
This doesn't seem to be specific to actions/checkout@v3 since we tried to upgrade to actions/checkout@v4 (here) and got the same failure (here).
v4 always used Node 20
I am having the same issue while running below versions, on ubuntu 20.04 VM:
Quoting the post paragraph about that workaround: "This will only work until we upgrade the runner removing Node16 later in the spring"
We are walking a tightrope.
Just wanted to raise some awareness about that. Plan to actually upgrade your github actions in the short term or move away from them. E.g. I think I'll quit my job. 😄
Reacted by GuyAv46, Felix Schwarz, Oskar Thornblad and Oriol Ricart Vilarrubias.
Reacted by Jozef Misutka, Jordi Vidal de LLobatera, Dave Berenbaum, Matthew Hinea and Joseph Birkner
/__e/node20/bin/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node)
Issue started today, i.e. 3 Jul 10am PDT.
My glibc version:
ldd --version
ldd (Ubuntu GLIBC 2.31-0ubuntu9.16) 2.31
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.
So why do I get this error? I am using [email protected]. I do not understand what I have to do to upgrade.
Here's a critical issue: Firstly, you shouldn't upgrade such fundamental environments arbitrarily. Even if you do upgrade, you must ensure the environment is correct. Upgrading to Node 20 and causing a glib error is absolutely unacceptable, especially in a product from a company like Microsoft.
Reacted by Rajeev Sarvaria, Emma Sax, Jean-Sébastien CONAN, Max M, Marshall Xu, ps-cbasketfield, Max Ustinov, Siim Kallas, Kiswono Prayogo, Vincent Moens and 1 more
I wish there was an alternative version of the checkout action, maybe written in rust so we could just deploy a static binary. Then we would just compile that against a really old version of glibc. This would also simplify running GitHub Actions with nektos/act which does not map node into the container.
Activity
[-]checkout@v3 using node20[/-][+]checkout@v3 using node20 instead of node16[/+]jcooke-impinj commentedon Jul 3, 2024
Our team found that setting these before starting the runners get's things going again. Still unsure what's causing this.
adpaco commentedon Jul 3, 2024
This doesn't seem to be specific to
actions/checkout@v3since we tried to upgrade toactions/checkout@v4(here) and got the same failure (here).biswalc commentedon Jul 4, 2024
I am having the same issue while running below versions, on ubuntu 20.04 VM:
Error:
Issue started today, i.e. 3 Jul 10am PDT.
junghyun2003 commentedon Jul 4, 2024
Hello! Our development team is also experiencing the same issue. We are using AWS instances as self-hosted.
We temporarily resolved the issue by simply changing the
node16directory tonode20in the same path. 🥲AWS AMI :
Git Action Error :
GuyAv46 commentedon Jul 4, 2024
Following this blog post: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Adding this to the envs that require node16 fixed the issue
Flamefire commentedon Jul 4, 2024
I tried setting this inside a workflow running on GH hosted runners and it didn't work.
So it looks like this only works when the runner itself was started with those set, i.e. you cannot set them for a running runner which includes the GH hosted ones.
v4 always used Node 20
See above
david-batranu commentedon Jul 4, 2024
Fixed by renaming the
node20folder and symlinkingnode16tonode20:eshogo commentedon Jul 4, 2024
I tried modifying /home/runner/actions-runner/.env and env.sh and it works fine.
and adding their environment variables into 'varCheckList' array in env.sh.
(not needed?)
Then restart runner service
david-batranu commentedon Jul 4, 2024
Looks like this is happening because of: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Workaround for docker CI failure (#6572)
n1ngu commentedon Jul 4, 2024
Quoting the post paragraph about that workaround: "This will only work until we upgrade the runner removing Node16 later in the spring"
We are walking a tightrope.
Just wanted to raise some awareness about that. Plan to actually upgrade your github actions in the short term or move away from them. E.g. I think I'll quit my job. 😄
biswalc commentedon Jul 4, 2024
My glibc version:
So why do I get this error? I am using [email protected]. I do not understand what I have to do to upgrade.
ayizhi commentedon Jul 5, 2024
Here's a critical issue: Firstly, you shouldn't upgrade such fundamental environments arbitrarily. Even if you do upgrade, you must ensure the environment is correct. Upgrading to Node 20 and causing a glib error is absolutely unacceptable, especially in a product from a company like Microsoft.
FelixSchwarz commentedon Jul 5, 2024
I wish there was an alternative version of the checkout action, maybe written in rust so we could just deploy a static binary. Then we would just compile that against a really old version of glibc. This would also simplify running GitHub Actions with nektos/act which does not map node into the container.
Update: I found checkout-action in GitHub's market place and added support for private repos. Not sure if that is a permanent solution but at least our CI jobs are passing again...
80 remaining items
chore: fix ci
chore: fix ci
Allowing unsecure node version due to actions/checkout#1809 (comment)
Update node16 check on self-hosted runners and remove python 3.6 (dee…
ci: tweak the dependabot config for branches a bit
ci: tweak the dependabot config for branches a bit
Attempt workaround from actions/checkout#1809
Revert "Attempt workaround from actions/checkout#1809"
ci: fix Ubuntu Bionic job
Fix release CI issues
Fix release CI issues (#673)
Fix nodejs/glibc problem with old container images. (coturn#1548)
Refactor CI workflows and fix failures due to Node.js 20 (coturn#1610, …
Update node16 check on self-hosted runners and remove python 3.6 (#5756)
Update node16 check on self-hosted runners and remove python 3.6 (#5756)