-
Notifications
You must be signed in to change notification settings - Fork 61
v1.0.2 requires a version of glibc that is not available on the current 'ubuntu-latest' Github runner #44
Comments
I am experiencing the same issue I think. Command as below. Is there a workaround? Neither of these are available to install via homebrew. I would be happy to run an older version if I can work out how to get it via the magic extension management mechanism. My development environment is based on Debian Buster so I can't containerise my way out of it. $ gh actions-cache list
/home/cefn/.local/share/gh/extensions/gh-actions-cache/gh-actions-cache: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/cefn/.local/share/gh/extensions/gh-actions-cache/gh-actions-cache)
/home/cefn/.local/share/gh/extensions/gh-actions-cache/gh-actions-cache: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/cefn/.local/share/gh/extensions/gh-actions-cache/gh-actions-cache) |
@cefn |
Hi @shabino your theory is correct. The cause for the issue is major changes from ubuntu-20 to ubuntu-22. |
Unfortunately attempting to install the prior version is non-functional with the suggested command, or a commit-based equivalent...
As an alternative I completed the following which resolved the issue.
|
@t-dedah our |
The version is 1.0.1 (not 1.01) |
Hi @shabino are you still facing this issue with |
@t-dedah Our ubuntu-latest is now 22.04.1, so this isn't an issue for us anymore. However, others stuck on older Linux distros will still have to pin to version 1.0.1. |
That's great @shabino. Yes, people with their self-hosted runners with older ubuntu versions will be stuck with v1.0.1. We will look if we can support older OS versions. |
Reproduction steps:
ubuntu-latest
gh actions-cache list
Expected behavior: My caches are listed.
Actual behavior:
Workaround:
I changed my job to use the
ubuntu-22.04
runner explicitly, and the problem resolved. It does seem that Github-provided extensions should work on the default runners though.Commentary:
It looks like Github is updating
ubuntu-latest
to 22.04 slowly:https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/
My repo has not yet been updated yet, but the gh-actions-cache repo has (see OS info within):
https://github.com/actions/gh-actions-cache/actions/runs/3567634871/jobs/5995563551
I suspect that the change to the glibc required version might be due to v1.0.2 being compiled on 22.04 while v1.01 likely was compiled on 20.04. A blog entry I found (note that I'm not a Go developer and can't evaluate this):
https://utcc.utoronto.ca/~cks/space/blog/programming/GoAndGlibcVersioning
Diagnostics:
I did my best to collect useful information below. However, I'm outside of my areas of expertise here, so please correct me!
v1.0.2 seemingly was compiled to require a newer version (2.3.2/2.3.4) of glibc (for some additional functions?) than was required by v1.0.1. This was problematic for us because the "ubuntu-latest" Github runner image is ubuntu-20.04 which supplies 2.3.1:
https://launchpad.net/ubuntu/focal/+source/glibc
Ubuntu 22.04 supplies version 2.3.5:
https://launchpad.net/ubuntu/jammy/+source/glibc
Output from my dev machine (against v1.0.1):
Output from my dev machine (against 1.0.2):
It appears that the version of glibc required for certain function invocations (pthread_create, etc.) increased in v1.0.2.
The text was updated successfully, but these errors were encountered: