Installation

Figure 785. Running a Docker container

docker run --detach ❶ \ 
  --name openldap ❷\
  -p 389:389 \ ❸
  --env LDAP_ORGANISATION="Betrayers heaven" \ ❹
  --env LDAP_TLS=false ❺\
  --env LDAP_DOMAIN="betrayer.com" ❻\
  --env LDAP_ADMIN_PASSWORD="secret" ❼\
  --env LDAP_CONFIG_PASSWORD="secret" ❽\ 
  --volume ~/OpenLdap/Data:/var/lib/ldap ❾\
  --volume ~/OpenLdap/Config:/etc/ldap/slapd.d ❾\
osixia/openldap:1.4.0 ❿

❶	Run the container and detach its process from the current shell. This will start a background process.
❷	The container's name to appear i.e. in a Docker listing: docker `container` `ls` CONTAINER ID IMAGE ... PORTS NAMES e82c438cda24 osixia/openldap:1.4.0 ... 0.0.0.0:389->389/tcp, 636/tcp openldap
❸	Bind the containers port 389 to the host system's port 389.
❹	The organisation's name e.g. “HdM Stuttgart”.
❺	We currently do not require transport layer security.
❻	The organisation's domain name. The corresponding DIT's root will be `dc=betrayer,dc=de`.
❼	The DIT's administrator password corresponding to the bind DN `cn=admin,dc=betrayer,dc=com`. This grants full access to the DIT starting at node `dc=betrayer,dc=com`.
❽	The server configuration tree's administrator password corresponding to an entirely distinct tree starting at `cn=config`. This tree among with its top level node of objectclass `olcGlobal` having RDN `cn=config` represents the server's configuration including: Schema classes. Access rules (permissions). Logging configuration. Search index definitions. Database backend parameters. `LDAP_CONFIG_PASSWORD` corresponds to the bind DN `cn=admin,cn=config` granting full access to the server's configuration tree.
❾	The docker host system's pre - existing directories `~/OpenLdap/Data` and `/~/OpenLdap/Config` will be mounted to the container's directories `/var/lib/ldap` and `/etc/ldap/slapd.d` respectively. Thus the OpenLdap server's back end databases will reside on the docker host system's file system. This allows for e.g. deleting and restoring the container without loosing data. This way your local server's database and the server's log files will exist outside your Docker container. This is not strictly required but allows to remove and re-install your container independently of its database. Note On windows make sure to execute from inside the Linux Sub System. This will allow for efficient file system access.
❿	The docker image name and version as being published on `https://hub.docker.com/r/osixia/openldap/tags`.

References:

osixia / docker-openldap documentation.
Docker container networking.
Docker run reference.

Caution

--detach is not documented in favour of its short variant -d.

Figure 786. Using docker-compose

version: '3.7'
  
services:
    openldap:
        image: osixia/openldap:1.4.0
        container_name: openldap
        restart: always
        environment:
            LDAP_ORGANISATION: "Betrayers heaven"
            LDAP_TLS: "false"
            LDAP_DOMAIN: "betrayer.com"
            LDAP_ADMIN_PASSWORD: "secret"
            LDAP_CONFIG_PASSWORD: "secret"
        ports:
            - 389:389
        volumes:
            - ~/OpenLdap/Data:/var/lib/ldap
            - ~/OpenLdap/Config:/etc/ldap/slapd.d

Figure 787. Installing Apache Directory Studio