Invoking one-touch Domino setup with system environment variables on Docker

Complete this procedure to invoke one-touch Domino setup with system environment variables if you run Domino on Docker.

Before you begin

Complete the following procedures:

Procedure

Run the following Docker command to create a new container and configure the Domino server inside the container using one-touch setup, leveraging environment variables defined in an environment file (env.txt in our example). The specified environment variables trigger and define the one-touch configuration. 
docker run -it -d -v <Docker volume name>:/local/notesdata --name <container name> --env-file env.txt -p <HostPort:ContainerPort> --stop-timeout=60 --cap-add=SYS_PTRACE domino-container:<image>
Note: If the specified Docker volume does not exist, it is automatically created.

For example:

docker run -it -d -v notesdata:/local/notesdata --name adminserver --env-file env.txt -p 1352:1352 -p 443:443 --stop-timeout=60 --cap-add=SYS_PTRACE domino-container:V1202
env.txt
SetupAutoConfigure=1
SERVERSETUP_SERVER_TYPE=first
SERVERSETUP_SERVER_NAME=domino-adminserver
SERVERSETUP_SERVER_DOMAINNAME=DominoDemo
SERVERSETUP_NETWORK_HOSTNAME=domino.demo.lab
SERVERSETUP_ORG_ORGNAME=DominoDemo
SERVERSETUP_ORG_CERTIFIERPASSWORD=domino4ever
SERVERSETUP_ADMIN_FIRSTNAME=Full
SERVERSETUP_ADMIN_LASTNAME=Admin
SERVERSETUP_ADMIN_PASSWORD=domino4ever
SERVERSETUP_ADMIN_IDFILEPATH=admin.id

Results

Your new Domino server should be up and running in a new Docker container.

What to do next

If one-touch setup fails for some reason, review the autoconfigure.log file created in the container by doing one of the following:
  • Copy the log file into the local file-system:
    docker cp adminserver:/local/notesdata/IBM_TECHNICAL_SUPPORT/autoconfigure.log /tmp
  • Invoke a shell into the still running container and navigate to the IBM_TECHNICAL_SUPPORT directory:
    docker exec -it adminserver bash