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
When I launch my container for the first time, I get no error, my custom schemas are copied correctly.
However, if I restart my container, I get this error :
Copy from internal path /assets/openldap/custom/schema to /container/run/service/slapd/assets/config/bootstrap/schema/custom
cp: cannot create directory '/container/run/service/slapd/assets/config/bootstrap/schema/custom': No such file or directory
*** ERROR | 2023-07-05 17:27:36 | /container/run/startup/slapd failed with status 1
I have the impression that on first startup the customs files are temporarily copied to the
/container/run/service/slapd/assets/config/bootstrap/schema/custom
that this folder disappears once the ldap base has been configured
Then, if I restart the container, it will no longer find these folders.
The text was updated successfully, but these errors were encountered:
Did you find any solution for this issue, i am fighting this since few days.
I did also try to use command: [ "--loglevel", "warning", "--copy-service" ] and still same issue.
openldap | Copy from internal path /assets/openldap/custom/schema to /container/run/service/slapd/assets/config/bootstrap/schema/custom openldap | cp: cannot create directory '/container/run/service/slapd/assets/config/bootstrap/schema/custom': No such file or directory openldap | *** ERROR | 2023-08-22 11:18:40 | /container/run/startup/slapd failed with status 1
We had the same issue. Got round it by setting the following:
LDAP_REMOVE_CONFIG_AFTER_SETUP=false
Also stopped mounting the schema and ldif files via volumes in docker compose, rather created our own docker image from osixia/openldap:1.5.0 and copying the schema and ldif files into that image.
When I launch my container for the first time, I get no error, my custom schemas are copied correctly.
However, if I restart my container, I get this error :
Copy from internal path /assets/openldap/custom/schema to /container/run/service/slapd/assets/config/bootstrap/schema/custom
cp: cannot create directory '/container/run/service/slapd/assets/config/bootstrap/schema/custom': No such file or directory
*** ERROR | 2023-07-05 17:27:36 | /container/run/startup/slapd failed with status 1
I have the impression that on first startup the customs files are temporarily copied to the
/container/run/service/slapd/assets/config/bootstrap/schema/custom
that this folder disappears once the ldap base has been configured
Then, if I restart the container, it will no longer find these folders.
The text was updated successfully, but these errors were encountered: