-
Notifications
You must be signed in to change notification settings - Fork 921
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
Github Actions Self-Hosted Runner issue with node 20 #3373
Comments
Same issue here with self-hosted runner. I am still running checkout@v2 and still its failing for node20. is it something to do with https://github.com/actions/runner/releases/tag/v2.317.0? |
Dropping support for official Are there plans to fix the |
Since node-based actions spread into containers, it seems very unwise to allow the node interpreter to rely on software inside the container. That appears to be the root of this mismatch. A container may contain older glibc which breaks things as basic as actions/checkout, which can leave users pretty trapped. Node should instead be:
|
With changes from GitHub [finally deprecating](actions/checkout#1474) [node16 based runners](https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/) (which the checkout@v3 action uses) we need to make changes to support this. To do this, there are two changes. First we remove the python 3.6 check as with the changes in pydantic v2 that will be merged soon, we will be removing this check there, so we can more easily remove it now so that future PRs are cleaner and it is clear why some changes have been made. Second, node16 is the default on some of our self-hosted runners. To work around tests failing on these, we [set the GitHub env var to override this check](https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/). Other relevant links: actions/checkout#1474 https://github.com/easybuilders/easybuild-framework/pull/4574/files actions/checkout#1809 actions/runner#3373 actions/checkout#1809
…rosoft#5756) With changes from GitHub [finally deprecating](actions/checkout#1474) [node16 based runners](https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/) (which the checkout@v3 action uses) we need to make changes to support this. To do this, there are two changes. First we remove the python 3.6 check as with the changes in pydantic v2 that will be merged soon, we will be removing this check there, so we can more easily remove it now so that future PRs are cleaner and it is clear why some changes have been made. Second, node16 is the default on some of our self-hosted runners. To work around tests failing on these, we [set the GitHub env var to override this check](https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/). Other relevant links: actions/checkout#1474 https://github.com/easybuilders/easybuild-framework/pull/4574/files actions/checkout#1809 actions/runner#3373 actions/checkout#1809
It appears this has actually been proposed in #3128 back in February. |
Describe the bug
I am running Github Actions Self Hosted Runner on a Ubuntu VM:
I am running Actions Runner version
2.317.0
In the context of the notice by the Github team: Notice
I am using the GitHub Actions:
But when the job executes, I get this Error in the Job logs:
On the Ubuntu VM, I have node installed already, and it is running as expected; not sure why the runner is complaining about not being able to run
node 20
Additional info:
Currently to circumvent the downtime of CI, I am running the scripts as below:
To Reproduce
Provided in the description.
Expected behavior
Since
node
versionv20.15.0
is already running on the ubuntu VM, the runner should not have issues with running withnode20
Runner Version and Platform
Github runner version
2.317.0
OS of the machine running the runner?
What's not working?
Provided in description.
Job Log Output
Runner and Worker's Diagnostic Logs
None
The text was updated successfully, but these errors were encountered: