Amir Rossert

@Legorooj Thanks for trying to help with this issue. I'm already aware of the `GLIBC` limitation that PyInstaller has, this is why I'm building my application on a docker container...

@Legorooj Thanks, I struggled before with `staticx` and couldn't make it work, I gave it another shot today and realized that it only works if PyInstaller is used in one...

I was able to pinpoint the module that causes this error, using [keyring](https://github.com/jaraco/keyring) is causing this: ``` import keyring ``` Building only this reproduces this error, I'm using version 18.0.1,...

@Legorooj I'm using `keyring` in my app so I cannot exclude it. I have done some more investigation around this, I have upgraded `libreadline.so` to version 8 so the file...

@htgoebel thanks a lot for your response. I have investigated it a bit more and have a full `strace` log of what is happening and will attach the log here....

@htgoebel I was finally able to locate the root cause of this error, it is not coming from `keyring` per se, `keyring` is using `platform.system()`, after looking at the source...

@jeremykatz Thanks for the reply, this issue with `sh` being linked to `libreadline` is still an issue for me to, changing the `LD_LIBRARY_PATH` before all imports is not a real...

+1

Is there any news about this?

@brifordwylie this looks like a good and useful addition, maybe create a PR to the maintainer.