version `GLIBC_2.34' not found (required by /tmp/_MEIXfEv3a/liblzma.so.5)

[liujin1993]

I build my python app in docker ubuntu:22.04， and run in a machine which is ubuntu16.
When executing "systemctl" in subprocess, the app report an error:

systemctl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /tmp/_MEIXfEv3a/liblzma.so.5)

My python file is:

import subprocess

print(1)
p = subprocess.Popen("systemctl status a", stdout=subprocess.PIPE, shell=True)
print(p.communicate())

[JonathonReinhart]

@liujin1993 This shouldn't happen, since staticx doesn't use LD_LIBRARY_PATH or any environment tricks that would persist into the child process.

What version of staticx are you using? How are you invoking staticx to build your app? Have you tried a debug build as noted in the docs?

[FirowMD]

Same, but in my case I've copied all dependencies located at /tmp/_MEIXXXXXX to /usr/lib/. The problem is libgcc_s.so.1 requires GLIBC_2.35.
But why I've copied *.so? Origin problem is following: when I call some shell command (like os.system('awk --help')) appears an error, which informs about missing libtinfo.so.6 (located at OS, which builds binary), but local installed awk has libncurses dependency and not libtinfo. Is there an option to call child processes with new environment like we do using terminal?

[FirowMD]

Solution is to use following code:

def run_cmd(s):
    subprocess.run(s.split(), env={})

run_cmd("awk --help")

[JonathonReinhart]

@FirowMD I believe your issue is related to PyInstaller and not Staticx, which does not modify the environment. See their docs where they suggest adjusting the environment for child processes: LD_LIBRARY_PATH / LIBPATH considerations

[JonathonReinhart]

Actually, @liujin1993 I think that is your issue also.

Staticx doesn't mess with LD_LIBRARY_PATH, but PyInstaller does. So when you go to execute a system binary from your Python code, you should make sure that LD_LIBRARY_PATH is not set: See LD_LIBRARY_PATH / LIBPATH considerations in the PyInstaller docs.

[FirowMD]

@FirowMD I believe your issue is related to PyInstaller and not Staticx, which does not modify the environment. See their docs where they suggest adjusting the environment for child processes: LD_LIBRARY_PATH / LIBPATH considerations

sure, I already solved it and pasted the solution above, which removes LD_LIBRARY_PATH using env={}

[JonathonReinhart]

which removes LD_LIBRARY_PATH using env={}

There's a prescribed method in their docs, but if you want to run your child process with a completely empty environment (no PATH, TERM, HOME, etc.), then go for it...