Skip to content
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Refactored the Dockerfiles and related
tooling to leverage Docker multi-stage build
functionality. Also updated base containers
to pick up later releases of Apache HTTP Server,
PHP, Shibboleth SP, and mod_auth_openidc.
1 contributor

Users who have contributed to this file

OpenLDAP slapd for COmanage Registry Volumes and Data Persistence

The OpenLDAP for COmanage Registry image requires two persistent directories into which state files will be written.

The persistent directories must be provided either using Docker volumes or bind mounts.

Note that when the image is only used as an LDAP proxy the persistent directories are not strictly necessary, provided all necessary configuration is injected at run time.

The paths for the directories inside the container that must be mounted are




For example to use bind mounts from the local Docker engine host:

sudo mkdir -p /opt/docker/var/lib/ldap
sudo mkdir -p /opt/docker/etc/ldap/slapd.d

and then when instantiating the container

docker run -d \
  --name comanage-registry-ldap \
  -v /opt/docker/var/lib/ldap:/var/lib/ldap \
  -v /opt/docker/etc/ldap/slapd.d:/etc/ldap/slapd.d \
  -p 389:389 \
  -p 636:636 \

After the image is instantiated into a container for the first time the entrypoint script will create the necessary base configuration, schema, and LMBD files for storing directory state, and bootstrap the directory using the values for the suffix, root DN, and root DN password injected at runtime using environment variables.

After the first instantiation of the container later restarts will not overwrite the suffix, root DN, and root DN password even if the values for the environment variables change.