Error when adding both a custom schema and data from ldif

[NekoLuka]

Hi,

While testing the current alpha image to see if it fits in our stack, I discovered the following error. Something seems to be going wrong in the startup.sh script related to loading the custom ldif files.

These are the logs produces by the image.

2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Container image: osixia/openldap:2.6.10-alpha
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Loading environment variables from /container/environment/.env, /container/environment/.env.bootstrap, /container/environment/.env.cron, /container/environment/.env.ctl, /container/environment/.env.upgrade ...
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Running /container/services/openldap/startup.sh ...
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Running /container/services/openldap-bootstrap/startup.sh ...
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Bootstrapping OpenLDAP ...
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Setting bootstrapping environment variables ...
2026-04-28 13:41:16 2026-04-28T11:41:16Z WARNING Generated config root password: pp9T0/qlYcaxNBkY
2026-04-28 13:41:16 2026-04-28T11:41:16Z WARNING Generated database root password: NNkJkcX5lNjqEuFn
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Creating OpenLDAP config ...
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Load /container/services/openldap-bootstrap/assets/ldif/config/base LDIFs ...
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Load /container/services/openldap-bootstrap/assets/ldif/config/refint LDIFs ...
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Load /container/services/openldap-bootstrap/assets/ldif/config/ppolicy LDIFs ...
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Load /container/services/openldap-bootstrap/assets/ldif/config/memberof LDIFs ...
2026-04-28 13:41:16 2026-04-28T11:41:16Z INFO    Load /container/services/openldap-bootstrap/assets/ldif/config/custom LDIFs ...
2026-04-28 13:41:17 2026-04-28T11:41:17Z INFO    Adding OpenLDAP data ...
2026-04-28 13:41:17 2026-04-28T11:41:17Z INFO    Load /container/services/openldap-bootstrap/assets/ldif/data/base LDIFs ...
2026-04-28 13:41:17 2026-04-28T11:41:17Z INFO    Load /container/services/openldap-bootstrap/assets/ldif/data/ppolicy LDIFs ...
2026-04-28 13:41:17 2026-04-28T11:41:17Z INFO    Load /container/services/openldap-bootstrap/assets/ldif/data/custom LDIFs ...
2026-04-28 13:41:17 2026-04-28T11:41:17Z INFO    Exiting ...
2026-04-28 13:41:17 /container/services/openldap-bootstrap/startup.sh: line 56: 10#schema: value too great for base (error token is "10#schema")
2026-04-28 13:41:17 /container/services/openldap-bootstrap/startup.sh: line 56: 10#database: value too great for base (error token is "10#database")
2026-04-28 13:41:17 2026-04-28T11:41:17Z ERROR   /container/services/openldap-bootstrap/startup.sh: exit status 1

This is my docker-compose:

volumes:
  conf:
  data:

services:
  openldap:
    image: osixia/openldap:2.6.10-alpha
    #restart: unless-stopped
    environment:
      OPENLDAP_BOOTSTRAP_ORGANIZATION: Sakuracloud
      OPENLDAP_BOOTSTRAP_SUFFIX: dc=sakuracloud,dc=nl

      OPENLDAP_BOOTSTRAP_REFINT: true
      OPENLDAP_BOOTSTRAP_PPOLICY: true
      OPENLDAP_BOOTSTRAP_MEMBEROF: true
    ports:
      - 389:3890
    volumes:
      - conf:/etc/openldap/slapd.d
      - data:/var/lib/openldap/openldap-data
      - ./schema.ldif:/container/services/openldap-bootstrap/assets/ldif/config/custom/schema.ldif
      - ./database.ldif:/container/services/openldap-bootstrap/assets/ldif/data/custom/database.ldif

The ldif files in question get easily imported by using slapadd and do not have syntax issues.

[BertrandGouny]

Hi,

Thanks a lot for reporting this issue 🙏

You’re absolutely right — the problem comes from the bootstrap script. It currently expects LDIF files to be prefixed with an ordering number (e.g. 00-, 10-, etc.), and it breaks when that’s not the case. This is clearly not very convenient for custom files like yours.

I’ll fix this so that LDIF files don’t require that naming convention and won’t cause the script to fail.

Thanks again for the feedback — this is very helpful 👍

[NekoLuka]

Thnx, I figured it out on my own. Another problem appears if you use a number < 10 (01,02,etc). Might also be of note

[BertrandGouny]

sorry for the noise just try to automate things with codex :D

[NekoLuka]

NP 😂