Open rohan-97 opened 1 week ago
Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.
If you think that's not the case and want to contribute a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.
With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.
Hi @carrodher - Can u please point me to the openldap doc link, which will help me to create the clustering with the common shared volume ?
Name and Version
bitnami/openldap2.6
What architecture are you using?
amd64
What steps will reproduce the bug?
/ldifs
directory and create another container image namedlocalhost:32000/custom-openldap
/root/openldap
)/root/openldap
) using the following commanddocker ps
commandWhat is the expected behavior?
The expected behaviour is that ldapsearch should work on all the pods correctly
What do you see instead?
Ldapsearch is working on one container image whereas on other container images, we see the following error
I wanted to know whether it is feasible/possible to use the same mount point for multiple bitnami containers.
Additional information
Following is the list of container images
And following is the ldapsearch output on all the containers:
search result
search: 2 result: 80 Other (e.g., implementation specific) error text: internal error
numResponses: 1
example.com
dn: dc=example,dc=com objectClass: top objectClass: domain dc: example
groups, example.com
dn: ou=groups,dc=example,dc=com objectClass: top objectClass: organizationalUnit ou: groups . . .