Giters

jetify-com / devbox

Instant, easy, and predictable development environments

Home Page:https://www.jetify.com/devbox/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

GLIBC patching and linker improvements

gcurtis opened this issue · comments

commented

Umbrella issue that tracks improvements to GLIBC patching.

Tasks
Beta Give feedback
  1. Preinstall common libraries for popular environments jetpack-io/devbox#1854
    feature linker python ruby
  2. Recreate virtual environments when changing packages jetpack-io/devbox#1855
    bug glibc linker linux python ruby
  3. Patch all packages that are using GCC libraries older than the stdenv libraries jetpack-io/devbox#1856
    feature glibc linker linux
  4. Stop setting LD_LIBRARY_PATH and LIBRARY_PATH jetpack-io/devbox#1798
    bug glibc linker linker/compiletime linux
    gcurtis
  5. Fix glibc-patch/flake.nix build jetpack-io/devbox#1857
    bug glibc linker linker/compiletime linux
    gcurtis
commented

I just stumbled on GLIBC issues with my current DevBox usage, and I'm unsure if this umbrella issue covers my use case. Would you be willing to chime in and give me some insight if that's the case? I could also start a new issue if that's desirable.

I'm doing a POC for my company where we are testing Devbox for local development and CI, but we need to deploy by building Docker Images on CI and moving the compiled static to the container. But we face version mismatches between the compiled and the container image GLIBC. For context, it is a Rust application.

I'm no Nix expert, so I have no idea of the feasibility of this, but it would be great if I could specify the targeted glibc version on devbox.json, and everything would just work as intended. Currently adding glibc pinned to a version breaks Devbox itself.