How to use this image

When a new container is created from the HCL Domino Docker image, it takes environment variables into account for auto-configuring the Domino server. Details on how to use those variables can be found here

The Domino data directory needs to be a persistent volume. On Docker it will be automatically created. You can also use an existing volume. All volume types your container infrastructure supports can be used.

Creating a new container from an image manually

Run a new Domino server with the configuration details of your choice. Make sure to specify the base image name at the very end of this command.

Note: For values containing blanks use quotes around the whole env parameter!

docker run -it -d \
     -e SetupAutoConfigure=1 \
     -e SERVERSETUP_ADMIN_PASSWORD=domino4ever \
     -e \
     -e SERVERSETUP_SERVER_NAME=domino-demo-v12 \
     -e \
    -h \
    -p 80:80 \
    -p 1352:1352 \
    -v dominodata_demo:/local/notesdata \
    --stop-timeout=60 \
    --cap-add=SYS_PTRACE \
    --cap-add=NET_BIND_SERVICE \
    --name domino12 \

Runtime configuration

During docker run you can setup a volume that mounts property files into /local/notesdata

Stopping the Application Server gracefully

Stopping a Domino server takes longer than the time a Docker server would expect by default (10 seconds), the recommended way is to add the parameter --stop-timeout already when starting the container. If the container was started with the parameter --stop-timeout= then you may stop the container using the following command:

docker stop <container-name>

If the container was started without specifying the parameter --stop-timeout= then use the following command to stop the container gracefully

docker stop --time=<timeout> <container-name>


docker stop --time=60 test