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:

• Preparing input parameters through system environment variables. Put the variables in a file such as env.txt. Each line of the file should have the form: name=value (no quotes). For example, a line of that file might be:

  SERVERSETUP_SERVER_TITLE=Renovations Mail Server

• Loading the Domino container image

1. Create a volume to store the Domino data directory. For example, to create a volume called notesdata, run the following Docker command:

docker volume create notesdata

docker run -it -v <Docker volume name>:<data directory> --name <container name> --env-file <env file name> -p <HostPort:ContainerPort> domino-docker:<image> --autoconf

For example:

docker run -it -v notesdata:/local/notesdata --name adminserver --env-file env.txt -p 8585:8585 -p 1352:1352 -p 443:443 domino-docker:V1200 --autoconf

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

If one-step setup fails for some reason, review theautoconfigure.log file created in the container. Since in this case the container won't be running, you can access the log file in one of the following ways:

• Create a temporary container:

  1. Run a Docker command to create a container that launches into a bash shell that uses the same volume you specified in the procedure. For example:

  
  docker run -it -v notesdata:/local/notesdata --name debug --entrypoint /bin/bash -p 8585:8585 -p 1352:1352 -p 443:443 domino-docker:V1200
  
  2. Examine IBM_TECHNICAL_SUPPORT/autoconfigure.log for details on the failure.
• Issue the following Docker command to copyautoconfigure.log out of the Docker volume into another path on the host:

  docker cp <container>:/file/path/within/container /host/path/target

  For example:

  docker cp adminserver:/local/notesdata/IBM_TECHNICAL_SUPPORT/autoconfigure.log C:\tmp

Related concepts
Domino on Docker