Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

checkout does not work on centos6 job container

See original GitHub issue

I’m trying to run workflows on custom docker images.

here’s my workflow:

https://github.com/chipitsine/haproxy/blob/master/.github/workflows/centos-6.yml

here’s error

https://github.com/chipitsine/haproxy/runs/449056642

Run actions/checkout@master
/usr/bin/docker exec  1057e0a52fb92dd983110f3493f46696ec0ba0293830256d3b1c11cac4da948d sh -c "cat /etc/*release | grep ^ID"
Running JavaScript Action with default external tool: node12
/__e/node12/bin/node: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by /__e/node12/bin/node)
/__e/node12/bin/node: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by /__e/node12/bin/node)
/__e/node12/bin/node: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.5' not found (required by /__e/node12/bin/node)
/__e/node12/bin/node: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /__e/node12/bin/node)
/__e/node12/bin/node: /lib64/libc.so.6: version `GLIBC_2.16' not found (required by /__e/node12/bin/node)
/__e/node12/bin/node: /lib64/libc.so.6: version `GLIBC_2.17' not found (required by /__e/node12/bin/node)
/__e/node12/bin/node: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /__e/node12/bin/node)
##[error]Node run failed with exit code 1

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:13 (5 by maintainers)

Top GitHub Comments

1reaction

ahvigilcommented, Aug 17, 2022

also running into this trying to build python wheels on manylinux containers- those containers are intentionally built with older versions of glibc, etc because trying to build wheels on more modern images gives errors such as

error: cannot repair X to "manylinux2010_x86_64" ABI because of the presence of too-recent versioned symbols. You'll need to compile the wheel on an older toolchain.

1reaction

snnncommented, Aug 6, 2020

we also currently don’t support redhat6 and centos6. AZP had to do another build of the runner and so far in actions, we’ve refrained from that. Increasing platform support is tracked in another issue.

Python’s official build environment(manylinux1 and manylinux2010) are still centos5 and centos 6. So they have a super large user base.

Top Results From Across the Web

github/git Checkout Returns 'error: invalid path' on Windows

After I opened an issue on the git-for-windows bug tracker (https://github.com/git-for-windows/git/issues/2803), I found that my issue had ...

Heartbeat not working on centos6 after last update

As for the customer case, please remember that we do not support heartbeat > in RHEL and that even resource-agents for pacemaker (the...

nodesource/centos6 - Docker Image

js within Docker containers that match the environments already being run within a company. These images give you great freedom in the Linux...

How To Limit Resources Using cgroups on CentOS 6

This package is not installed by default on a CentOS 6 server. To install it, run the following command: sudo yum install libcgroup....

rhel6/rhel - Certified Container Image

This base image provides your operations and application teams with the packages, language runtimes and tools necessary to run, maintain, and troubleshoot all ......