Executables with shared libraries fail to run with err "no such file or directory"

[eljamm]

@rgoulter

I notice the dynamic linker ld-linux-x86-64.so.2 resolves to a different path for some reason

The same thing happened in:

Build go code within a nix shell

We’ve been investigating since yesterday about the issue, without much luck. I made a quick reproducer here: Go in a Nix Shell · GitHub Running this code on my own NixOS laptop but also on my own Amazon Workspace (based on RedHat) works pretty fine. I don’t think the issue is related to Nix at all since the beginning. [image] However, running exactly the same steps on his Amazon Workspace (based on Ubuntu) doesn’t work: ❯ git clone https://gist.github.com/drupol/e8db5a7e22611d3aa9cd94ca5ac…

So there is definitely something wrong there. Both programs deal with a "net/http" server so I wonder how that relates.

@rgoulter

Using patch-elf --set-interpreter with this /nix/store/35pq....p4am-glib-2.39-5/ didn’t result in the same error, either.

That’s true. I couldn’t reproduce the error with this either, but perhaps this is not the main cause, but an rather an effect.

Here is my take on why it wasn’t working based on these two threads:

• wrong version of glibc gets picked as an interpreter
• this version doesn’t exist (anymore? after gc?) on the machaine
• user tries to run the binary, but interpreter is not found
• no such file or directory error

How to reproduce?

• $ nix run nixpkgs#patchelf – --set-interpreter “/hello/world” ./main
• $ ./main
• $ zsh: no such file or directory: ./main
• now, replace “/hello/world” with a glibc that no longer exists and you’ll have the same issue

Solutions?

• re-install the system → correct linker gets picked
• install another glibc → its linker gets picked? fixes the first issue?