vrajnys/openldap-debian repository overview

⁠OpenLDAP Server with Log Rotation and Customizable Volumes

This Docker image provides a lightweight OpenLDAP server based on Debian 12 (Bookworm), offering customizable configuration, data storage, and automatic log rotation. It is designed for easy setup and integration into a variety of environments.

⁠Key Features

• Custom Configuration: Override the default OpenLDAP configuration by mounting your own configuration files to /etc/ldap/slapd.d. By default, an admin user (admin/admin) is created on the first run.
• Persistent Data Storage: Ensure LDAP data persists across container runs by mounting an external volume to /var/lib/ldap.
• Log Management: OpenLDAP logs are stored in /logs/slapd.log. Logs are automatically rotated using logrotate to prevent disk space issues. You can remount /logs for external log management.

⁠Usage

To run the LDAP server with custom configuration, data, and log directories, use the following command:

docker run -d \
    -v /path/to/config:/etc/ldap/slapd.d \
    -v /path/to/data:/var/lib/ldap \
    -v /path/to/logs:/logs \
    ldap-server

⁠Mountable Directories

• /etc/ldap/slapd.d: Mount this directory to override the default OpenLDAP configuration.
• /var/lib/ldap: Mount this directory to store your LDAP data persistently.
• /logs: Mount this directory to manage OpenLDAP logs externally.

⁠Default Admin User

By default, the container creates an admin user with full privileges:

    Admin DN: cn=admin,dc=nodomain
    Password: admin

This can be customized by providing your own configuration during initialization.

⁠Log Rotation

OpenLDAP logs are stored in /logs/slapd.log and automatically rotated daily using logrotate. You can customize the log directory and manage logs externally by remounting /logs to an external location. Example

To start the container with custom volumes:

docker run -d \
    -v /my/config:/etc/ldap/slapd.d \
    -v /my/data:/var/lib/ldap \
    -v /my/logs:/logs \
    ldap-server

This setup ensures that your configuration, data, and logs are managed independently of the container lifecycle.