Skip to content
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

Open
jcooke-impinj opened this issue Jul 3, 2024 · 40 comments
Open

checkout@v3 using node20 instead of node16 #1809

jcooke-impinj opened this issue Jul 3, 2024 · 40 comments

Comments

@jcooke-impinj
Copy link

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)

@jcooke-impinj
Copy link
Author

Our team found that setting these before starting the runners get's things going again. Still unsure what's causing this.

export ACTIONS_RUNNER_FORCED_INTERNAL_NODE_VERSION=node16
export ACTIONS_RUNNER_FORCE_ACTIONS_NODE_VERSION=node16

@adpaco-aws
Copy link

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).

@biswalc
Copy link

biswalc commented Jul 4, 2024

I am having the same issue while running below versions, on ubuntu 20.04 VM:

actions/[email protected]
actions/checkout@v3
actions/checkout@v4
actions/[email protected]

Error:

/__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.

@junghyun-apr
Copy link

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. 🥲

AWS AMI :

amzn2-ami-kernel-5.10-hvm-2.0.20240223.0-x86_64-gp2

Git Action Error :

/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)

@GuyAv46
Copy link

GuyAv46 commented 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

ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true

@Flamefire
Copy link

Flamefire commented Jul 4, 2024

Our team found that setting these before starting the runners get's things going again. Still unsure what's causing this.

export ACTIONS_RUNNER_FORCED_INTERNAL_NODE_VERSION=node16
export ACTIONS_RUNNER_FORCE_ACTIONS_NODE_VERSION=node16

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:

actions/[email protected]
actions/checkout@v3
actions/checkout@v4
actions/[email protected]

See above

@david-batranu
Copy link

Fixed by renaming the node20 folder and symlinking node16 to node20:

cd $RUNNER_HOME/actions-runner/externals
mv node20 node20.bak
ln -s node16 node20

@eshogo
Copy link

eshogo commented Jul 4, 2024

I tried modifying /home/runner/actions-runner/.env and env.sh and it works fine.

% cat .env
ACTIONS_RUNNER_FORCED_INTERNAL_NODE_VERSION=node16
ACTIONS_RUNNER_FORCE_ACTIONS_NODE_VERSION=node16

and adding their environment variables into 'varCheckList' array in env.sh.
(not needed?)

varCheckList=(
    'LANG'
    'JAVA_HOME'
    'ANT_HOME'
    'M2_HOME'
    'ANDROID_HOME'
    'ANDROID_SDK_ROOT'
    'GRADLE_HOME'
    'NVM_BIN'
    'NVM_PATH'
    'LD_LIBRARY_PATH'
    'PERL5LIB'
    'ACTIONS_RUNNER_FORCED_INTERNAL_NODE_VERSION'
    'ACTIONS_RUNNER_FORCE_ACTIONS_NODE_VERSION'
    )

Then restart runner service

% systemctl restart github-actions-runner.service

@david-batranu
Copy link

@n1ngu
Copy link

n1ngu commented 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

ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true

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
Copy link

biswalc commented Jul 4, 2024

I am having the same issue while running below versions, on ubuntu 20.04 VM:

actions/[email protected]
actions/checkout@v3
actions/checkout@v4
actions/[email protected]

Error:

/__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.

@ayizhi
Copy link

ayizhi commented 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
Copy link

FelixSchwarz commented 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...

@hasufell
Copy link

hasufell commented Jul 5, 2024

This means you now can't run any docker image that has a glibc older than 2.27. That includes:

  • debian:9
  • fedora:27
  • ubuntu:18.04

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?

hasufell added a commit to stable-haskell/haskell-language-server that referenced this issue Jul 5, 2024
hasufell added a commit to haskell/ghcup-metadata that referenced this issue Jul 5, 2024
huonw pushed a commit to pantsbuild/pants that referenced this issue Jul 25, 2024
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]>
huonw pushed a commit to pantsbuild/pants that referenced this issue Jul 25, 2024
We started to run into issues with node16 no longer being functional on
the runner, with symptoms like
actions/checkout#1809
huonw pushed a commit to pantsbuild/pants that referenced this issue Jul 25, 2024
We started to run into issues with node16 no longer being functional on
the runner, with symptoms like
actions/checkout#1809
huonw added a commit to pantsbuild/pants that referenced this issue Jul 25, 2024
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]>
huonw added a commit to pantsbuild/pants that referenced this issue Jul 25, 2024
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]>
OCopping added a commit to OCopping/pvxs that referenced this issue Jul 31, 2024
Uses a fix for actions/checkout mentioned in actions/checkout#1809
kriszyp added a commit to kriszyp/lmdb-js that referenced this issue Aug 2, 2024
eakraly pushed a commit to coturn/coturn that referenced this issue Aug 4, 2024
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.
bruderj15 added a commit to bruderj15/Hasmtlib that referenced this issue Aug 16, 2024
KMarshallX referenced this issue in KMarshallX/VesselBoost Aug 19, 2024
@maksadbek
Copy link

maksadbek commented Nov 10, 2024

I'm really confused trying to understand how these workflows work:

# This workflow will build a golang project
# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-go

name: Go

on:
  push:
    branches: [ "main" ]
  pull_request:
    branches: [ "main" ]

jobs:

  build:
    runs-on: ubuntu-20.04
    container: ubuntu:16.04
    steps:
    - uses: actions/checkout@v2

    - name: Set up Go
      uses: actions/setup-go@v4
      with:
        go-version: '1.20'

    - name: Build
      run: go build -v ./...

    - name: Test
      run: go test -v ./...

it's failing with the glibc not found error:

Run actions/checkout@v2
/usr/bin/docker exec  d5bc5bba7bd6d0c36d05f01be4cc266534953c3a2647d4acc3e553c2fa07eacc sh -c "cat /etc/*release | grep ^ID"
/__e/node20/bin/node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /__e/node20/bin/node)
/__e/node20/bin/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node)
/__e/node20/bin/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /__e/node20/bin/node)

but the action.yml of V2 versions states it must use node12: https://github.com/actions/checkout/blob/v2/action.yml#L75

I can't believe that Github Actions has changed ALL versions of actions/checkout to use node20

fendor added a commit to haskell/haskell-language-server that referenced this issue Nov 11, 2024
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
fendor added a commit to fendor/haskell-language-server that referenced this issue Nov 11, 2024
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
derevnjuk pushed a commit to NeuraLegion/bright-cli that referenced this issue Nov 11, 2024
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests