Unable to mount my custom ldif file

[dayadev]

How do we mount our own ldif file. It looks like, no matter what my file contents are, its always return the ldap data from osixia/openldap

[kstotz]

Hello!

I need a little bit more information if possible please.

I also seem to be stuck here, unable to get my ldif file to load.

Just how exactly is this
bootstrap.ldif /container/service/slapd/assets/config/bootstrap/ldif/50-bootstrap.ldif
mounted?

I see within the Docker file the line:

copy bootstrap.ldif /container/service/slapd/assets/config/bootstrap/ldif/50-bootstrap.ldif

But yet when I shell into the LDAP container I see no directory such as /container/service/slapd/assets/config.

I also see that the startup script is failing according to these log file entries:

*** INFO | 2022-09-05 18:23:02 | Start OpenLDAP...
*** INFO | 2022-09-05 18:23:02 | Waiting for OpenLDAP to start...
*** INFO | 2022-09-05 18:23:02 | Add bootstrap schemas...
config file testing succeeded
*** INFO | 2022-09-05 18:23:02 | Add image bootstrap ldif...
*** ERROR | 2022-09-05 18:23:02 | /container/run/startup/slapd failed with status 68
*** INFO | 2022-09-05 18:23:02 | Killing all processes...

Thanks in advance :)

[wshihadeh]

The easiest way to do this is like described below

• checkout this repo
• update bootstrap.ldif with your own data and make sure that it is a valid LDIF file
• update Makefile with your docker image info
• execute the following commands

make build
make push

or just make release

from the below error, i can tell that there is an issue with the bootstrap file (syntax error)

*** ERROR | 2022-09-05 18:23:02 | /container/run/startup/slapd failed with status 68

[kstotz]

Wow, thanks so much for you time on my behalf. I can only hope this discussion might help others as well.

This is great advice, to just kind of start over as you suggest above so as to get back to known ground.

Your observation about the 'failed status 68' error helps greatly. However inspecting my file I see no obvious typos or other potential problems (although there must be something). I suspected the issue was due to the bootstrap.ldif not actually getting copied into the correct place within the container because when I shelled into the container to look, I found no /container/service/slapd/assets/config directory.

Knowing that the issue might be a malformed bootstrap.ldif file also gives me a straw to clutch onto. Thanks again for your time.