mbixtech/389ds repository overview

⁠389 Directory Server Container

⁠Available Platform

The container image is built based on Fedora version 33 and available on platform below.

• Intel/AMD x86_64

⁠Usage

⁠Docker

Use docker command to run container image, e.g.

docker run -it --rm -e ROOT_PW=manager -e FQDN_NAME=389ds.example.com -p 3389:389 -p 3636:636 --name 389ds mbixtech/389ds

For example data of dc=example,dc=com

docker exec -it 389ds bash
/root/create-example-suffix.sh
/root/create-example-db.sh
/root/create-example-entries.sh

⁠Docker compose

Edit environment variables in docker-compose.yml file and run as e.g. below.

docker-compose up

For example data of dc=example,dc=com

docker-compose exec dirsrv bash
/root/create-example-suffix.sh
/root/create-example-db.sh
/root/create-example-entries.sh

⁠Limitation

• First time startup, the container will initialize 389 directory server instance. There will be errors related to systemd service and fips. It would be ignored due to it is not available in container.
• Secure connection will be initialized at first time startup. It uses self-signed certificate with 240 months validity from first startup. You can replace it with your prefer external CA and external server certificate. You must setup persistent volume before replacement.
• Changing FQDN_NAME variable after first startup, it will not change the server certificate. You must manually change it. For self-signed server certificate, you can follow /root/create-selfsigned-cert.sh file as a given example.
• There is no suffix and database after first startup. You must create suffix, database and some entries up to your requirement. However, there are example scripts to create suffix, database and entries for dc=example,dc=com. You see it in Usage section above.
• Cockpit for 389 directory server is not available in this container image.