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

"'GLIBC_2.38' not found" when installing Python 3.10 on container derived from python:3.10-slim #11666

Open
2 of 5 tasks
lpascal-ledger opened this issue Jan 22, 2025 · 6 comments

Comments

@lpascal-ledger
Copy link

Hello there 👋 Thanks for the action, very useful! We've encountered a strange bug today:

Description:

We're using setup-python in a matrix to test our product on several Python versions.

The tests were running in a container derived from python:3.9-slim, where we previously installed all our tools. We were running tests with Python 3.8, 3.9, 3.10 and 3.11 and all was working fine.

Today we updated this image to python:3.10-slim, but now when we setup Python 3.10, python crashes when invoked.

Our tests also run with Python 3.11 setup which does not trigger this issue.

Action version:

actions/setup-python@v5

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:

Repro steps:

I've tried and cornered the issue in the following workflow which triggers the bug:

name: Debug
on:
  workflow_dispatch:
  push:

jobs:
  not_working:
    runs-on: ubuntu-latest
    container:
      image: python:3.10-slim
    steps:
      - uses: actions/setup-python@v5
        with:
          python-version: "3.10"
      - run: python

An example of this failing workflow can be found here.

Expected behavior:

Python can be invoked without error.

Actual behavior:

When invoked, python crashes with the following errors:

python: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /__t/Python/3.10.16/x64/lib/libpython3.10.so.1.0)
python: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /__t/Python/3.10.16/x64/lib/libpython3.10.so.1.0)
Error: Process completed with exit code 1.
@lpascal-ledger lpascal-ledger added bug Something isn't working needs triage labels Jan 22, 2025
@lpascal-ledger lpascal-ledger changed the title "GLIBC_2.38' not found" when installing Python 3.10 on container derived from python:3.10-slim` "'GLIBC_2.38' not found" when installing Python 3.10 on container derived from python:3.10-slim Jan 22, 2025
@priya-kinthali
Copy link

Hello @lpascal-ledger👋,
Thank you for reporting this issue. We will investigate it and get back to you as soon as we have some feedback.

@mbrsamsung
Copy link

We are getting something that looks alot like this, but this occurs when running with ubuntu-latest with a debian bookworm based image. When setting the machines to ubuntu-22.04 the issue is not present.

@lmvysakh
Copy link

lmvysakh commented Feb 7, 2025

Hi @lpascal-ledger,

As the GLIBC library and other packages and tools have been removed from Ubuntu 24 due to maintenance and efforts to reduce the image size, we suggest using Ubuntu 22 or Ubuntu 20 runners to resolve this issue.

Please find the updated workflow and a screenshot for your reference:

name: Debug

on:
  workflow_dispatch:
  push:

jobs:
  not_working:
    runs-on: ubuntu-22.04
    container:
      image: python:3.10-slim
    steps:
      - uses: actions/setup-python@v5
        with:
          python-version: "3.10"
      - run: python

Image

Thank you for your understanding. Please feel free to reach out if you have any further concerns or need additional clarification!

@RemDelaporteMathurin
Copy link

Hi! I recently experienced the same issue. Is there a long term plan for this or do we have to roll back to Ubuntu 22? Thanks for the help!

@lmvysakh
Copy link

Hy @lpascal-ledger,

Our initial investigation was conducted on GitHub Hosted Ubuntu runners, and we found no discrepancies related to glibc with the Ubuntu 20 and 22 runners.

Since the Ubuntu 20 and 22 runners are operating correctly, the issue might be specific to the Ubuntu 24 runner. Therefore, we are transferring this issue to the runner images team.

@HarithaVattikuti HarithaVattikuti transferred this issue from actions/setup-python Feb 25, 2025
@vidyasagarnimmagaddi vidyasagarnimmagaddi self-assigned this Feb 26, 2025
@vidyasagarnimmagaddi
Copy link
Contributor

Hi @lpascal-ledger , Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating.


Faraz32123 pushed a commit to edly-io/h5pxblock that referenced this issue Mar 4, 2025
Faraz32123 pushed a commit to edly-io/h5pxblock that referenced this issue Mar 4, 2025
ziafazal pushed a commit to edly-io/h5pxblock that referenced this issue Mar 4, 2025
* fix: delete cloud files only if the path exists

- `storage.listdir(path)` throws an error for the path As for the first time path doesn't exists on S3. Error: `NoSuchKey: An error occurred (NoSuchKey) when calling the ListObjects operation: The specified key does not exist`.
- In this commit, added a check if the specific path does exists or not before deleting the previously added content on that path.

* fix: CI failure occurring due to Ubuntu 24 runner.

- CI is failing here: https://github.com/edly-io/h5pxblock/actions/runs/13648230543/job/38151064603 and it's explanation can be found here: actions/runner-images#11666 (comment) along with it's fix.

* chore: version bump

---------

Co-authored-by: Muhammad Faraz  Maqsood <faraz.maqsood@A006-01130.local>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants