-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
/__e/node20/bin/node: /lib/x86_64-linux-gnu/libc.so.6: version
GLIBC_2.28' not found (required by /__e/node20/bin/node)`
#1590
Comments
I also have this problem on Ubuntu 22.04 (see https://github.com/briandfoy/data-constraint/actions/runs/7645971689/job/20833756885 while it is around).
|
I have the same issue when trying to use ubuntu:18.04 image |
See actions/checkout#1590 Signed-off-by: falkTX <falktx@falktx.com>
Similarly the |
See actions/checkout#1590 Signed-off-by: falkTX <falktx@falktx.com>
I have the same problem with checkout@v4 with running CI on ubuntu:16.04 and ubuntu:18.04 docker images:
https://github.com/Lastique/scope/actions/runs/7754629439/job/21148329132
https://github.com/Lastique/scope/actions/runs/7754629439/job/21148329685 These older Ubuntu images are needed to be able to test older compiler versions. Until this issue is resolved, please remove the deprecation notice for checkout@v3, as there simply is no alternative. |
…ngs." This reverts commit a8750d5. checkout@v4 doesn't work on ubuntu:16.04 and ubuntu:18.04 images: actions/checkout#1590
note that it is not just the checkout being broken, anything that uses node is broken which includes cache and artifacts. basically all the v4 actions from github are broken for older distros due to glibc requirements |
basically all the v4 actions from github are broken for older distros due to glibc requirements
Yes. I've noticed. Obviously this was the first one I diagnosed, so it got the issue :)
|
Same problem in ubuntu 18 |
Anyone found a workaround for this? Or know why it started happening? |
the workaround is to keep using v3 actions. and it happens because github devs updated the base system where their node stack is built from. seeing the way github has handled other issues, I expect this one to just be ignored completely. |
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
This fixes the deprecation warnings for actions/checkout@v3. actions/checkout@v4 is not functional because of the upstream bug: actions/checkout#1590
Avoid errors like > /__e/node20/bin/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node) when using Ubuntu 16/18 containers with the @v4 actions See actions/checkout#1590
The centos:7 build no longer works on github due to this: Run actions/checkout@v3 /usr/bin/docker exec 02e2cf2da72963d76b12a421e48bc0790138ee97bf567c8afcdf792dbc2093d8 sh -c "cat /etc/*release | grep ^ID" /__e/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /__e/node20/bin/node) See actions/checkout#1590 Attempt to work around this by allowing an "insecure" node version. Signed-off-by: John Levon <john.levon@nutanix.com>
|
The centos:7 build no longer works on github due to this: Run actions/checkout@v3 /usr/bin/docker exec 02e2cf2da72963d76b12a421e48bc0790138ee97bf567c8afcdf792dbc2093d8 sh -c "cat /etc/*release | grep ^ID" /__e/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /__e/node20/bin/node) See actions/checkout#1590 Attempt to work around this by allowing an "insecure" node version. Signed-off-by: John Levon <john.levon@nutanix.com>
The centos:7 build no longer works on github due to this: Run actions/checkout@v3 /usr/bin/docker exec 02e2cf2da72963d76b12a421e48bc0790138ee97bf567c8afcdf792dbc2093d8 sh -c "cat /etc/*release | grep ^ID" /__e/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /__e/node20/bin/node) See actions/checkout#1590 Attempt to work around this by allowing an "insecure" node version. Signed-off-by: John Levon <john.levon@nutanix.com>
The centos:7 build no longer works on github due to this: Run actions/checkout@v3 /usr/bin/docker exec 02e2cf2da72963d76b12a421e48bc0790138ee97bf567c8afcdf792dbc2093d8 sh -c "cat /etc/*release | grep ^ID" /__e/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /__e/node20/bin/node) See actions/checkout#1590 The workaround suggested there does not work, at least for centos:7. Instead, we'll open-code the checkout operation instead of using the github action. For the other jobs, which still work for now, move to the non-deprecated checkout@v4. Signed-off-by: John Levon <john.levon@nutanix.com>
The centos:7 build no longer works on github due to this: Run actions/checkout@v3 /usr/bin/docker exec 02e2cf2da72963d76b12a421e48bc0790138ee97bf567c8afcdf792dbc2093d8 sh -c "cat /etc/*release | grep ^ID" /__e/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /__e/node20/bin/node) See actions/checkout#1590 The workaround suggested there does not work, at least for centos:7. Instead, we'll open-code the checkout operation instead of using the github action. For the other jobs, which still work for now, move to the non-deprecated checkout@v4. Signed-off-by: John Levon <john.levon@nutanix.com>
Same problem
Has anyone solved this? |
@backend-sungjin as it's clear they're not planning to fix this, I'd recommend dropping use of this action altogether. |
Also, CentOS 7 has reached end-of-life. |
We are on v3 and encountering this error as well. I may have to pin down the specific v3 version that does not introduce this breaking change. No mention of breaking changes in the change logs either. |
FYI, pinning down the version didn't seem to work (I pinned down to v3.5.0), so assuming node20 is required to build the container in checkout, can possibly set the node version in VM to 20 first then to an older version if the rest of the jobs depend on an older node version. |
(Of course this will just get overwritten by haskell-ci, but maybe by that time the bug actions/checkout#1590 will have been fixed.)
The thing is it may not always checkout the latest or the commit before a feature branch commit? |
Avoid errors like > /__e/node20/bin/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node) when using Ubuntu 16/18 containers with the @v4 actions See actions/checkout#1590
Avoid errors like > /__e/node20/bin/node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node) when using Ubuntu 16/18 containers with the @v4 actions See actions/checkout#1590
The tests in Bionic fail due to a problem in nodejs. Found a workaround at the end of actions/checkout#1590 It consists on disable using node20 and allow using an insecure version of nodejs.
The tests in Bionic fail due to a problem in nodejs. Found a workaround at the end of actions/checkout#1590 It consists on disable using node20 and allow using an insecure version of nodejs.
The tests in Bionic fail due to a problem in nodejs. Found a workaround at the end of actions/checkout#1590 It consists on disable using node20 and allow using an insecure version of nodejs.
hey team, any updates on this? It's being 9 months and this issue has been referenced in hundreds of issues/prs |
There are no updates and there won't be any. They are deprecating these releases. They allowed people to use them for a while through a special flag that was supposed to give you one last deadline extension. I do not agree with this decision, but this is how it works. They have a legitimate need to keep the number of supported configurations down to a reasonable number. The only compromise I see possible is for Github to allow actions to use an existing Node.js runtime in the container through a flag - just as they can use an existing |
for issue, see canonical/snapd-glib#171 for fix
I ran into this bug for some CI tests and I implemented a workaround. We basically built (but did not push) a docker image and ran the CI tests inside of the docker build. If the CI tests passed, then the docker build was successful. If the CI tests failed, then the docker build failed. In this way we got around the node js version limitations for actions/checkout. |
i use container to test build on old compiler, but when use checkout action i take the error about nodejs. |
Using
container:
image: debian:bullseye
to build the OpenJDK for an older release of a distro (Debian in this case, but this isn't specific to Debian) causes a failure due tonode
in theactions/checkout@v4
docker image to fail to run due to the container having an older glibc:(Using build tools that depend on newer glibc versions seems likely to be a common pitfall for GitHub Actions.)
The text was updated successfully, but these errors were encountered: