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@v4 is not working in containers #1487

Open
mneraki-philips opened this issue Sep 19, 2023 · 12 comments
Open

checkout@v4 is not working in containers #1487

mneraki-philips opened this issue Sep 19, 2023 · 12 comments

Comments

@mneraki-philips
Copy link

Hi Team,

our workflows are getting failed with this error. "GLIBC_2.27' not found" everything was fine with checkout@v3, but after the update its getting failed.

image

@damyan
Copy link

damyan commented Sep 20, 2023

Same here running runner with image actions-runner-dind:v2.308.0-ubuntu-20.04

@PowellNGL
Copy link

I've also encountered this problem today with a container based on oraclelinux:7.9. It seems like old container distros just aren't supported any more because of the upgrade to node20

@damyan
Copy link

damyan commented Sep 22, 2023

I have the same on ubuntu 22.04-based containers

@bwiczkowsk96
Copy link

I have same issue.. Needed to switch to GH runners from self hosted.

@MahdiBM
Copy link

MahdiBM commented Oct 12, 2023

Same here. Using v4, runs-on: ubuntu-latest and container: swift:5.9-amazonlinux2.
The url to action failure: https://github.com/vapor/penny-bot/actions/runs/6498712580/job/17650628177

@damyan
Copy link

damyan commented Oct 24, 2023

Related: actions/runner#2844 got reverted, s. actions/runner#2918

@mdrocan
Copy link

mdrocan commented Nov 2, 2023

Still seeing this issue with ubuntu-latest, using the container public.ecr.aws/sam/build-python3.9

@white-eagle-83
Copy link

is this fix published in any version yet?

@mdrocan
Copy link

mdrocan commented Nov 9, 2023

Myself reverted all actions to checkout@v3 as those seem to work without a problem.

kgreav added a commit to zepben/.github that referenced this issue Nov 15, 2023
Signed-off-by: Kurt Greaves <kurt.greaves@zepben.com>
@sethrj
Copy link

sethrj commented Nov 19, 2023

I have this issue when running a CentOS 7 (AMD ROCm) container but not an Ubuntu 20 (CUDA) container.

@mloskot
Copy link

mloskot commented Dec 23, 2023

Seems like a duplicate of

ylobankov added a commit to tarantool/tarantool that referenced this issue Mar 13, 2024
It's impossible to run Node.js 20 actions on CentOS 7 due to issue [1].
So if we want to upgrade to Node.js 20 actions, we have to drop testing
on CentOS 7 in the packaging workflow. Otherwise, the testing job fails
with the following error:

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

[1] actions/checkout#1487

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci
ylobankov added a commit to tarantool/tarantool that referenced this issue Mar 13, 2024
It's impossible to run Node.js 20 actions on CentOS 7 due to issue [1].
So if we want to upgrade to Node.js 20 actions, we have to drop testing
on CentOS 7 in the packaging workflow. Otherwise, the testing job fails
with the following error:

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

[1] actions/checkout#1487

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci
ylobankov added a commit to tarantool/tarantool that referenced this issue Mar 13, 2024
It's impossible to run Node.js 20 actions on CentOS 7 due to issue [1].
So if we want to upgrade to Node.js 20 actions, we have to drop testing
on CentOS 7 in the packaging workflow. Otherwise, the testing job fails
with the following error:

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

[1] actions/checkout#1487

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci
ewdurbin added a commit to pypi/warehouse that referenced this issue Mar 14, 2024
ylobankov added a commit to tarantool/tarantool that referenced this issue Mar 14, 2024
It's impossible to run Node.js 20 actions on CentOS 7 due to issue [1].
So if we want to upgrade to Node.js 20 actions, we have to drop testing
on CentOS 7 in the packaging workflow. Otherwise, the testing job fails
with the following error:

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

[1] actions/checkout#1487

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci
ewdurbin added a commit to pypi/warehouse that referenced this issue Mar 14, 2024
* lets just try dockah

* here

* hm?

* ghcr?

* login

* use da cache

* hehe

* f

* perms

* big dumb

* oh lala

* hipshot

* ?

* that's no kubes

* oh yeah

* connect up da services

* oh that is simpler

* paths?

* restore da matrix, neo

* hmmmmm

* don't locale me

* maybe bash

* omfg

* straws!

* restore matrix, neo

* hmmmmmmmmmm

* ooo

* hold on docs 4 now

* split up docs stuff

* GHA doesn't have git anymore

* i hate this uid/gidshit

* 🤦

* just skip for now

* whoami

* pro

* allup

* CI!!!

* cache it all

* Revert "GHA doesn't have git anymore"

This reverts commit 157441b.

* mount the whole shebang

* env in container

* wront spot

* argumentsssss

* am fog

* hm

* no?

* when in doubt

* ?

* ?

* set it aside for now

* okay now to fight git?

* hold

* ref: actions/checkout#1487

* allup

* byapss

* validate

* No, I will not be squashing all that, witness my garbage.

* not sure if neccessary

* too slow and doesn't capture RUN caches anyway

* nose clean

* no, we wanted that :)

* oh, right this is what enables the gha docker cache

* more caching cannot hurt

* test cachin

* oh, right

* Revert "test cachin"

This reverts commit f03fd35.

* test all the caches

* test the caches

* test cache

* test caching and validate deps task

* test test test

* reverts

* test code only change

* does caching work in container runs?

* revert test change
ylobankov added a commit to tarantool/tarantool that referenced this issue Mar 14, 2024
It's impossible to run Node.js 20 actions on CentOS 7 due to issue [1].
So if we want to upgrade to Node.js 20 actions, we have to drop testing
on CentOS 7 in the packaging workflow. Otherwise, the testing job fails
with the following error:

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

[1] actions/checkout#1487

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

(cherry picked from commit 4f8701b)
ylobankov added a commit to tarantool/tarantool that referenced this issue Mar 14, 2024
It's impossible to run Node.js 20 actions on CentOS 7 due to issue [1].
So if we want to upgrade to Node.js 20 actions, we have to drop testing
on CentOS 7 in the packaging workflow. Otherwise, the testing job fails
with the following error:

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

[1] actions/checkout#1487

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

(cherry picked from commit 4f8701b)
@sameeraksc
Copy link

We also have this issue. Github is saying v3 is deprecated. But no one can use v4

VariantXYZ added a commit to Medabots/medarot4 that referenced this issue Jul 14, 2024
VariantXYZ added a commit to Medabots/medarot4 that referenced this issue Jul 14, 2024
sebsto added a commit to sebsto/swift-aws-lambda-runtime that referenced this issue Oct 10, 2024
sebsto added a commit to swift-server/swift-aws-lambda-runtime that referenced this issue Oct 10, 2024
* add aws sdk example

* add soto example

* use amazonlinux docker image instead of ubuntu

* dynamically add runtime dependency based on env var

* remove import of Foundation.ProcessInfo

* workaround actions/checkout#1487
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

10 participants