latest nightly release fails in CI during foundryup

[alvrs]

Component

Foundryup

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

No response

What version of Foundryup are you on?

No response

What command(s) is the bug in?

No response

Operating System

Linux

Describe the bug

Our CI recently started failing with this error while installing foundry nightly via the foundry-rs/foundry-toolchain@v1 github action:

. prepare: forge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by forge)
. prepare: forge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by forge)

(See https://github.com/latticexyz/mud/actions/runs/13909195313/job/38919307523#step:5:119)

It works correctly when pinning foundry to version nightly-f47d7e0c29a36372908b917cd74aa589d5888f8e. (See latticexyz/mud#3628)

[mattsse]

likely related #10098

[grandizzy]

@alvrs it doesn't seem that foundry toolchain fails but pnpm install --frozen-lockfile, what runner do you use? We had to update to Ubuntu 22.04 to be able to build so most probably you use an older one, can you try updating?

[alvrs]

Why do you think it's pnpm install --frozen-lockfile that's failing? This the output i see right before the error:

prepare$ husky install && (forge --version || pnpm foundryup)
. prepare: husky - Git hooks installed
. prepare: forge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by forge)
. prepare: forge: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by forge)
. prepare: forge: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by forge)
. prepare: > mud-monorepo@ foundryup /home/runner/work/mud/mud
. prepare: > curl -L https://foundry.paradigm.xyz/ | bash && bash ~/.foundry/bin/foundryup
. prepare:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
. prepare:                                  Dload  Upload   Total   Spent    Left  Speed
. prepare:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
. prepare: 100   167  100   167    0     0   2734      0 --:--:-- --:--:-- --:--:--  2737
. prepare: 100  2196  100  2196    0     0  17997      0 --:--:-- --:--:-- --:--:-- 17997
. prepare: Installing foundryup...
. prepare: Detected your preferred shell is bash and added foundryup to PATH.
. prepare: Run 'source /home/runner/.bashrc' or start a new terminal session to use foundryup.
. prepare: Then, simply run 'foundryup' to install Foundry.
. prepare: bash: /home/runner/.foundry/bin/foundryup: No such file or directory
. prepare:  ELIFECYCLE  Command failed.
. prepare: Failed
 ELIFECYCLE  Command failed with exit code 1.
Error: Process completed with exit code 1.

This is running on a depot.dev with ubuntu-22.04-16.

The reason why I think it has to do with a recent nightly release is that it works without issues when pinning to nightly-f47d7e0c29a36372908b917cd74aa589d5888f8e from 2 days ago (using the same runner and same repo on our side, see latticexyz/mud#3628)

[grandizzy]

I meant it doesn't fail in foundry-rs/foundry-toolchain@v1. We had to build with different runner (different gibc) hence why it works without an older build. Any chance you could check with an Ubuntu 24.02 then?

[grandizzy]

Made some tests and indeed it works on ubuntu 24.04 but fails for 22.04 and 20.04 due to glibc version

• fails with ubuntu-20.04: https://github.com/grandizzy/release-workflow/actions/runs/13917435868/job/38942949156#step:4:7
• fails with ubuntu-22.04: https://github.com/grandizzy/release-workflow/actions/runs/13917453542/job/38942998327
• works with ubuntu-24.04: https://github.com/grandizzy/release-workflow/actions/runs/13917468505/job/38943038788