[distribution] Link release binaries statically against glibc

[darestov]

Description

I cannot run foundry on an older Debian, it complains about wrong glibc version. However, I absolutely cannot update the system.

On the other hand, Foundry by all means feels like a script program. Should be independet of a system. Can it be linked statically so as to run on a system with any Glibc version? Or (even) can it be rewritten as a Bash script?

Additional context

No response

[Nageshbansal]

Hey @darestov, thanks for the report.

Our release pipeline was building the linux/amd64 binary with cgo enabled, which linked it against the build machine's glibc. That is why it refuses to start on older systems. The fix is in #186: releases get built statically, so the binary will run on any glibc version, and on distros without glibc at all.

That lands in the next release. Until then, the arm64 artifact is already static and unaffected, so that one works if it matches your machine.

On the bash script idea, that is the direction we deliberately moved away from (SigNoz/signoz#10924).