-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/wordpress-nginx] error while loading shared libraries: libldap_r-2.4.so.2: cannot open shared object file: No such file or directory #63502
Comments
Hi @g-vdn, Thank you for getting in touch. I have attempted to replicate the issue, but unfortunately, I was not able to reproduce it. I used the docker-compose.yml file and deployed wordpress-nginx:latest, and WordPress responded without any issues:
Additionally, please note that you have the option to enhance the image with extra libraries by customizing it. You can refer to the customization guide at https://github.com/bitnami/containers/tree/main/bitnami/wordpress-nginx#customize-this-image for instructions on extending the image. I hope this information assists you in resolving your issue. |
Hi @fevisera, Replying quite late, had some RAM issues which crashed the server on which container is running. Thanks for looking into this. I am using unRAID hypervisor, it's kinda picky when you are not installing dockers from the Community Apps, I installed this image from Docker hub, manually set-up each ENV var I thought is needed, and worked fine for a while, I created a wordpress site, test it, etc. I don't work actively on it, so no idea when this issue happened exactly, but now I am stuck with this Not very good with dockers at this point, I know just little above the basics. Seems to me that library missing from host OS, am I correct in this? |
Hi @g-vdn, No problem. That library seems to be available in the latest container:
Could you try using the latest container version (6.4.3-debian-12-r0), available a couple of days ago, and check if the error persist? If the error persists, it would be greatly appreciated if you could share the details of the container configuration (such as environment variables, configuration files, etc.) that are being set up, so that I can attempt to reproduce the issue. Thanks! |
Hi @fevisera Here are the environment variables used: Till now I was using latest image, now used debian one which you mentioned, same thing What config files would you need? I have 2 persistent locations mapped, as is visible in XML. Let me know which you need and I'll share. Thanks! |
Hi, The Regarding the config file, I'm not sure how you are providing an XML for configuring the container. Could you share more details on how you are deploying the container? |
Hi @fevisera , I am running the container under unRAID hypervisor, running Slackware OS
Docker version: Here is the output of docker inspect, hope this will provide more useful data for you
|
Hi @g-vdn, Could you share the exact steps to reproduce the error? We may be missing something because the docker image includes You can check that the library is there by doing the following, mentioned previously:
|
Hi @fevisera, Figured out the issue, /opt/bitnami was mapped as persistent storage. Before: After: Thanks a lot for your assistance |
Hi @g-vdn, I'm glad you were able to resolve it and thank you for providing additional details. Please note that you can find further information on persisting application data at https://github.com/bitnami/containers/tree/main/bitnami/wordpress-nginx#persisting-your-application. Since the issue has been resolved, I will proceed to close it. Please, feel free to reach out again with any other issues. |
Name and Version
bitnami/wordpress-nginx:latest
What architecture are you using?
amd64
What steps will reproduce the bug?
After the latest update, the docker image running on unRAID will not start
The container was functional before
What is the expected behavior?
For the container to start
What do you see instead?
The text was updated successfully, but these errors were encountered: