foundry: forge fails with `GLIBC_2.33' not found (required by forge) in github action CI
Component
Forge
Have you ensured that all of these are up to date?
- Foundry
- Foundryup
What version of Foundry are you on?
nightly-2e99f7fdaef6a7aaeb426b02ef87e052cc14f68b
What command(s) is the bug in?
No response
Operating System
Linux
Describe the bug
We use the foundry-toolchain github action in our CI and it started failing in the last few hours with failures like this:
forge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by forge)
forge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by forge)
forge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by forge)
Is there a problem with the nightly release?
I didn’t include the proper forge --version string, because forge can’t even run that in our CI. It started failing after the latest release:
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 6
- Comments: 55 (28 by maintainers)
Commits related to this issue
- fix: solidity-foundry.yml workflow See https://github.com/foundry-rs/foundry/issues/3827, looks like the appropriate glibc is not found on `ubuntu-latest`. — committed to smartcontractkit/chainlink by makramkd 2 years ago
- ci: fix glibc error https://github.com/foundry-rs/foundry/issues/3827 — committed to paradigmxyz/reth by gakonst 2 years ago
- ci: pin ubuntu to 20.04 to avoid glibc errors ref: https://github.com/paradigmxyz/reth/actions/runs/5486255403/jobs/9996118421 ref: https://github.com/foundry-rs/foundry/issues/3827 Compiling serde ... — committed to paradigmxyz/reth by gakonst a year ago
- ci: pin ubuntu to 20.04 to avoid glibc errors ref: https://github.com/paradigmxyz/reth/actions/runs/5486255403/jobs/9996118421 ref: https://github.com/foundry-rs/foundry/issues/3827 Compiling serde ... — committed to paradigmxyz/reth by gakonst a year ago
Note by GitHub: This comment was written directly on a roller-coaster.
https://twitter.com/transmissions11/status/1599203404383162369
We’re on it - thx for the patience and debug info all.
FYI: I have just faced the same error locally when cloning and installing repo. Once I upgraded from Ubuntu 20.04 to 22.04 (on WSL) everything is back to normal.
Hey. We noticed a similar issue in our CI for
dappyesterday. @elopez found a workaround with: https://github.com/crytic/crytic-compile/pull/320, the same trick might work for foundryPSA: please add “runs-on: ubuntu-22.04” in your CI.
It looks like it’s fixed it for a few people and the person that said it didn’t work above seems to be having a different issue (unclear if related or not).
Here’s how @mattsse did it https://github.com/foundry-rs/foundry/commit/36276aac0408fde8b00c19e2cfc3b7bec3fc429d
@tsarbuig Add
runs-on: ubuntu-22.04to the github actions job - that was the temporary fix here for foundry, but it should be fine for everyone now with the latest releases. If you’re running into this with ethers.rs I’d suggest raising an issue there and pointing at this thread?Seems fixed for
slither-actionat least!Updating to Ubuntu 22.04 images on CircleCI fixed this issue for us.
Thanks, @gakonst – I think the release file should be sufficient. Just whatever machine these binaries are built on should be pinned to ubuntu 20.04. Appreciate y’alls quick efforts here.
Facing similar issue when running ``foundryup`
A dump of all erorrs =
https://pastebin.com/raw/iW7V5Em6Solutions which worked –
This one was run with 20.04 as well:
https://github.com/foundry-rs/foundry/actions/runs/3597605800/jobs/6059525485
only the latest switched to 22.04, so this seems to be the cause.
I think this is mostly forwards compatible, so I wonder if we should pin the release runner to
20.04for the time being.