Ruby 2.7 throws the error `GLIBC_2.38' not found about devbox

[gcurtis]

@jamesgecko I can't seem to reproduce this issue from a clean ARM64 Linux VM. Couple of followup questions:

1. Were you ever using a different version of Ruby in this project before switching to [email protected]?
2. Were there any other packages that had been in the devbox.json that you've since removed?
3. Did you already try deleting .devbox/virtenv/ruby_2_7/ and then re-running bundle install && bundle exec rails?

I'm wondering if there was a package that put a newer version of gcc/glibc in $DEVBOX_PACKAGES_DIR/lib at one point. This would've caused bundler to compile/link the gems with GLIBC 2.38. But if that package got removed later, then the newer GLIBC would no longer be available.

[jamesgecko]

To create the reproduction, I started a brand new devbox project and copy/pasted the devbox.json file from my original project into it. There was no preexisting .devbox for this project.

In the original project directory, I tried all sorts of different stuff in devbox.json. In this stack trace it's a date gem crashing. In the original project it was a postgresql gem crashing.

Is it possible there's something in my host NixOS setup that is problematic with the devbox environment? I thought that programs.nix-ld.enable = true; (used for remotely connecting with VSCode) might be problematic, but I disabled it. ran sudo nixos-rebuild switch, rebooted the vm, deleted .devbox, and things are still broken.

I'm wondering if there's something getting cached in my home directory that could be causing this? But another Rails devbox project I have that uses Ruby 3.1.3 is fine.

[gcurtis]

I upgraded my NixOS and now I'm able to reproduce it. I think I know why this is happening. When bundler installs the gems, it's using the stdenv's gcc which is linking against glibc 2.38. However, the ruby interpreter itself is linked against glibc 2.37.

I'm going to try out a couple potential fixes and see if something works.