fix(release): build Linux CLI on ubuntu-22.04 (glibc 2.35) so binaries run on older distros#2330
Open
r266-tech wants to merge 1 commit into
Open
Conversation
… glibc-2.39 runners (refs vectorize-io#2321)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem (#2321)
The released Linux
hindsightCLI binaries are built by therelease-rust-clijob on glibc-2.39 GitHub runners:x86_64-unknown-linux-gnu→ubuntu-latest(= Ubuntu 24.04, glibc 2.39)aarch64-unknown-linux-gnu→ubuntu-24.04-arm(glibc 2.39)cargo build --releaselinks dynamically against the build host's glibc, so the shipped binary requiresGLIBC_2.39, which only Ubuntu 24.04 / Debian 13 provide. On anything older it fails at startup exactly as reported:Fix
Pin both Linux build legs to ubuntu-22.04 (glibc 2.35), the oldest GitHub-hosted Ubuntu runner:
ubuntu-latest→ubuntu-22.04(amd64)ubuntu-24.04-arm→ubuntu-22.04-arm(arm64)ubuntu-22.04-armis a maintained GitHub-hosted arm64 runner label (actions/runner-images), so the arm64 leg keeps shipping. NoCargo.toml/ TLS / dependency changes. macOS targets are untouched.This restores runnability on Ubuntu 22.04+, Debian 12, RHEL/Rocky/Alma 9, etc.
Scope / what this does not cover
The reporter's
### Option Asuggested Ubuntu 20.04 (glibc 2.31), but GitHub retired theubuntu-20.04hosted runner in April 2025, so 22.04 (glibc 2.35) is the lowest floor reachable with hosted runners. This therefore does not fix systems on glibc < 2.35 — Ubuntu 20.04 (2.31), Debian 11, RHEL/CentOS 8 (2.28), or Alpine.For full coverage including those, the reporter's
### Option B(the fully-staticx86_64-unknown-linux-musltarget) is the complete fix. That's a larger change —hindsight-clipullsreqwestwith default features (native-tls/OpenSSL), so musl-static would meandefault-features = false+rustls-tls, i.e. a TLS-stack swap worth reviewing on its own. Happy to send that as a follow-up if you'd prefer the broader floor; this PR is the clean, low-risk improvement that fixes the large majority of current LTS/enterprise deployments.Addresses #2321 (leaving the issue open in case you want the musl path for glibc < 2.35).