You need to use an explicit invocation of the dynamic linker, so something like this:
/home/glibc/lib/ld-linux-x86-64.so.2 --library-path /home/glibc/lib /usr/bin/python
(But the fact that the GLIBC_2.4 symbol version is not available suggests that something is very wrong with the new glibc, or it is actually not very new at all, predating glibc 2.4.)
» pip install glibc
GLIBC >=2.39 python container?
Building Python 3.11.1 on Centos7 with alternative glibc (2.29)
GLIBC issue
How to choose which GLIBC_version in python when I use blender to render with python - Stack Overflow
You need to use an explicit invocation of the dynamic linker, so something like this:
/home/glibc/lib/ld-linux-x86-64.so.2 --library-path /home/glibc/lib /usr/bin/python
(But the fact that the GLIBC_2.4 symbol version is not available suggests that something is very wrong with the new glibc, or it is actually not very new at all, predating glibc 2.4.)
If you compiled glibc yourself you should have testrun.sh script in your build directory. This is simpler and more reliable than using ld-linux.so:
build/testrun.sh ls
In short, a django backend needs to run an arm64 binary file, interaction works on host with no problems.
Right now I'm building the django container from python:latest, which has glibc 2.36, but the binary has 2.39 dependencies.