profanity-im
Profanity fails to start due to missing shared library libpython3.11.so.1.0 (debian container)
Expected Behavior
Profanity should start successfully without missing library errors when executed from within the debian Docker container.
### Current Behavior
Running ./profanity within a Docker container results in an error:
./profanity: error while loading shared libraries: libpython3.11.so.1.0: cannot open shared object file: No such file or directory
Possible Solution
It seems that the libpython3.11.so.1.0 library is not installed or is not in the expected path. Possible solutions could include:
Installing the correct version of Python and its libraries within the Docker container.
Updating the Dockerfile to ensure all dependencies are correctly installed.
Steps to Reproduce (for bugs)
Build the Docker image for Profanity with Dockerfile.debian.
Run the image and access the container:
sudo docker run -it profanity /bin/bash
Attempt to start Profanity:
`./profanity`
Observe the error regarding the missing libpython3.11.so.1.0 library.
Context
This issue prevents Profanity from starting in the debian Docker environment, blocking usage and testing within the container. Environment
Profanity, version 0.14.0dev.master.313ab5d5
Copyright (C) 2012 - 2019 James Booth <[email protected]>.
Copyright (C) 2019 - 2024 Michael Vetter <[email protected]>.
License GPLv3+: GNU GPL version 3 or later <https://www.gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Build information:
XMPP library: libstrophe
Desktop notification support: Enabled
OTR support: Enabled (libotr 4.1.1)
PGP support: Enabled (libgpgme 1.18.0)
OMEMO support: Enabled
C plugins: Enabled
Python plugins: Enabled (3.11.2)
GTK icons/clipboard: Disabled
GDK Pixbuf: Enabled
