Open drunksaint opened 4 years ago
Hi @drunksaint,
The problem is that there's a mismatch between the glibc
version on your computer and on Lambda.
This is slightly different from the issue we were having with Nuitka. Although PyInstaller has packed all the necessary libraries into the executable, it still relies on the host's glibc
. The package was created on a system with glibc
v2.25, but Lambda comes with v2.17.
The easiest solution, I think, is to run PyInstaller in the same runtime environment as Lambda, which typically requires starting a new EC2 instance with the proper image.
Also, take a look at the first question here. There's a second solution based on StaticX which allows you to also packet your own gblic
in the binary.
--Sadjad
Ah I see, building it on ec2 with the aws linux 1 ami fixed the pyinstaller issue!
Looks like binaries built with pyinstaller also have an issue running on lambda because of missing libs. The error I'm getting:
My wrapper file:
I built the pyinstaller binary with
pyinstaller --onefile pifiletest.py --distpath .