You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After setting up this container we were also spinning up a fusiondirectory container pointing to that openldap-fusiondirectory backend.
With the openldap-fusiondirectory container version 1.4-7.1.5 the custom init scripts are not executed.
Summary
After setting up this container we were also spinning up a fusiondirectory container pointing to that openldap-fusiondirectory backend.
With the openldap-fusiondirectory container version 1.4-7.1.5 the custom init scripts are not executed.
Steps to reproduce
First spin up the openldap-fusiondirectory setup:
Then spin up the fusiondirectory UI:
What is the expected correct behavior?
The login through the fusiondirectory UI is possible.
The scripts being executed, so that the fusiondirectory UI can actually access.
Relevant logs and/or screenshots
While starting the docker container the first time, the logs show:
After getting a listing of the custom-scripts directory within the container it shows that the scripts are not executable:
Environment
Any logs | docker-compose.yml
Possible fixes
Not only chmod +x /usr/sbin/fusiondirectory-insert-schema but also
chmod +x
the other necessary scripts.Actually, adding the line in the Dockerfile worked for me:
The text was updated successfully, but these errors were encountered: