Linux release binaries require glibc >= 2.38
- Dominant language
- CSS
- Stars
- 1
- Forks
- 0
- Avg merge
- 26m
- Merged PRs (30d)
- 62
Description
Found verifying the 0.1.0 release, pre-existing since rc.1: Linux binaries are built on ubuntu-latest (24.04, glibc 2.39) and require glibc >= 2.38. They fail on Debian 12 bookworm (2.36) and Ubuntu 22.04 LTS (2.35) with:
```text
beam.smp: /lib/x86_64-linux-gnu/libc.so.6: version 'GLIBC_2.38' not found
```
The cherry-dev image itself (bookworm) cannot run its own release binary. Fix: pin the Linux release-build jobs to older runners (or an older-glibc container) so the floor drops to something Debian-stable users have. Candidate for a 0.2.1 patch release; needs a CI assertion on the resulting binary's glibc floor so it never regresses.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Linux release-build jobs in the CI configuration and reviewing how the cherry-dev image runs the release binary. Rebuild with an older runner or glibc environment, verify the binary runs on Debian 12 and Ubuntu 22.04, and add a CI assertion that catches a higher glibc floor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, linux
- Domain
- build-system, ci-cd, operating-systems, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100