Creating a temporary container to set up the trial server
To deploy a new Domino trial server as a Docker container, first create a temporary container to complete remote Domino server setup.
About this task
- Use the docker run command with the arguments described in this procedure to create a container that runs Domino that enables you to run remote server setup. Only remote server setup is supported; the Docker-compatible Red Hat Universal Base Image (UBI) doesn't contain the required X11 libraries to support Graphical User Interface (GUI) and display. For additional information on docker run, see Docker run command arguments in the main Domino Docker documentation.
- If you are setting up an additional server in the domain and the server ID is not stored in the Domino directory, have the server ID available; you will use the docker cp command in this procedure to copy the server ID file to the Domino volume.
- If the Domino server ID is password-protected and you plan to run the Domino container in detached mode (-d) you must create a secrets file to store the password. If you create the secrets file manually, have the the file available; you will use the docker cp command in this procedure to copy the file to the Domino volume. For more information, see Creating a secrets file for a password-protected server ID in the main Domino docker documentation.
- After remote server setup completes (succesfully or not) the container stops. The command in this procedure includes the --rm argument to then remove the container, which is no longer needed.
- Remote server setup requires only ports 8585 and 1352 so there is no need to specify additional ports.
Procedure
-
To determine the name of the Domino Docker image (required for the next step),
from the Docker terminal window, issue the following command to list the names
of the Docker images on your system.
docker image ls
-
To create and run a container to complete server setup, issue the following
command:
The following example creates and runs the containerdocker run --rm --name <container name> -v <Docker volume name>:<data directory> -v <full path to license key file>:/local/notesdata/trial_account.txt --hostname <your_hostname> -p 8585:8585 -p 1352:1352 <image> --setup
dominosetup
based on the imagedomino-docker:V120_06102021prodtrial-all
using the trial license key filetrial_account.txt
in/tmp
of the host systemdocker.renovations.com
. It creates the data directory/local/notesdata
, referred to by the volume namednotesdata
.docker run --rm --name dominosetup -v notesdata:/local/notesdata -v /tmp/trial_account.txt:/local/notesdata/trial_account.txt --hostname docker.renovations.com -p 8585:8585 -p 1352:1352 domino-docker:V120_06102021prodtrial-all --setup
Note: To avoid date-time conflicts, Docker containers should run in the same time zone as the host system. By default, the Domino trial docker container is in the UTC time zone. If your host system is not in UTC, add the parameter-v /etc/timezone:/etc/timezone:ro
to the run command to mount the/etc/timezone
config file from your host system into the Domino trial container in read-only mode:docker run --rm --name <container name> -v <Docker volume name>:<data directory> -v <full path to license key file>:/local/notesdata/trial_account.txt -v /etc/timezone:/etc/timezone:ro --hostname <your_hostname> -p 8585:8585 -p 1352:1352 <image> --setup
-
The Domino server launches in listen mode. Before running remote server setup,
complete the following steps if necessary. Otherwise, skip this step.
-
Run remote server setup. For more information, see Using the Domino server setup program remotely in the
main Domino installation documentation.
Note: During remote server setup, Select Web Browsers (HTTP services) on the "What internet services should this Domino Server provide?" dialog box.
Results
After you complete server setup, the container stops and is removed.