-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
checkout@v3 using node20 instead of node16 #1809
Comments
Our team found that setting these before starting the runners get's things going again. Still unsure what's causing this.
|
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. |
Hello! Our development team is also experiencing the same issue. We are using AWS instances as self-hosted. AWS AMI :
Git Action Error :
|
Following this blog post: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
I tried setting this inside a workflow running on GH hosted runners and it didn't work.
v4 always used Node 20
See above |
Fixed by renaming the cd $RUNNER_HOME/actions-runner/externals
mv node20 node20.bak
ln -s node16 node20 |
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.
Then restart runner service
|
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/ |
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. 😄 |
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. |
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. |
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... |
This means you now can't run any docker image that has a glibc older than 2.27. That includes:
What a huge f*ckup. I'm baffled by the amount of incompetence. What's wrong with providing a statically linked node binary? Do you need help with redistribution github? |
We started to run into issues with node16 no longer being functional on the runner, with symptoms like actions/checkout#1809 Co-authored-by: Andreas Stenius <[email protected]>
We started to run into issues with node16 no longer being functional on the runner, with symptoms like actions/checkout#1809
We started to run into issues with node16 no longer being functional on the runner, with symptoms like actions/checkout#1809
We started to run into issues with node16 no longer being functional on the runner, with symptoms like actions/checkout#1809 Co-authored-by: Andreas Stenius <[email protected]>
We started to run into issues with node16 no longer being functional on the runner, with symptoms like actions/checkout#1809 Co-authored-by: Andreas Stenius <[email protected]>
Uses a fix for actions/checkout mentioned in actions/checkout#1809
This problem is caused by this issue: actions/checkout#1809 Several comments include documentation on various environment variables to force it to use the older nodejs release still, but probably those various workarounds will stop working eventually.
I'm really confused trying to understand how these workflows work:
it's failing with the glibc not found error:
but the I can't believe that |
Some release jobs have to be executed on a custom runner due to GitHub forcing a newer nodejs version: actions/checkout#1809 This whole issue is a huge rabbit hole where you can get lost. In short: * The actions/checkout@4 versions require the nodejs 20 version * Prebuilt nodejs 20 are linking against a newer GLIBC version * Even though jobs are executed in a docker image, some commands are from the runner machine, (e.g. nodejs is from the ubuntu-latest runner). * Downgrading to actions/checkout@3 worked for some time. However, due to https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/ it seems like we *have* to do something. Thus, we are running jobs for older distro images on a customer runner, provided by maerwald. In particular, when writing this message, the distro images that have be run on the custom runner are: * debian:9 * ubuntu:18.04 * mint:19.3 * fedora:27 * centos:7
Some release jobs have to be executed on a custom runner due to GitHub forcing a newer nodejs version: actions/checkout#1809 This whole issue is a huge rabbit hole where you can get lost. In short: * The actions/checkout@4 versions require the nodejs 20 version * Prebuilt nodejs 20 are linking against a newer GLIBC version * Even though jobs are executed in a docker image, some commands are from the runner machine, (e.g. nodejs is from the ubuntu-latest runner). * Downgrading to actions/checkout@3 worked for some time. However, due to https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/ it seems like we *have* to do something. Thus, we are running jobs for older distro images on a customer runner, provided by maerwald. In particular, when writing this message, the distro images that have be run on the custom runner are: * debian:9 * ubuntu:18.04 * mint:19.3 * fedora:27 * centos:7
e2e pipeline fails on Ubuntu 16.04 and 18.04 due to the recent default switch to node20 in actions/checkout. Node20 requires GLIBC 2.28 or higher, which these environments lack. To resolve this, we’re setting the `ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true` environment variable to allow fallback to a compatible Node version, restoring pipeline stability. Useful links: * [GitHub changelog: node20 default](https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/) * [GitHub issue #1809](actions/checkout#1809)
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)The text was updated successfully, but these errors were encountered: