HCL Domino is available as a container image that can be used with current Docker or Podman runtimes. HCL Domino is preinstalled on this image, allowing you to deploy Domino servers as containers with just a few commands.

As of Domino 12.0.2, the container image is based on the HCL open source domino-container project.

This documentation provides information on common functionality. Other available features are documented by the https://opensource.hcltechsw.com/domino-container/.

Note: The image is available for download through the HCL Licensing Portal.

To get started, here are some container terms that are useful to know.

• image A file that contains a built, executable version of an application. Images are uploaded to Docker and used to create and run containers.
• container An isolated location on a Docker host that contains the executable software and files required to run an application. Containers exclude unnecessary files managed by the host operating system.
• volume A location on Docker that stores data to be read or written by the application.While containers are easily deleted and recreated, volumes persist. The Domino data directory is stored in a volume and you can act on the corresponding Domino container without affecting the contents of the volume.
• Docker daemon The Docker service that you interact with through the docker commands to create and manage containers. Also referred to as the Docker Engine.
• Docker host The physical computer that runs the Docker daemon.
• Podman is an alternative runtime, providing the same commands. Replace "docker" with "podman" for the commands issued.

Domino on Docker requirements
Understand the requirements and current limitations for Domino on Docker.

Docker run command arguments
To create containers for Domino, you use the the docker run command with the following arguments.

Creating a secrets file for a password-protected server ID
If a Domino server ID is password-protected and you run the Domino container in detached mode where an administrator cannot input the password directly, create a secrets file to store the password. The Domino server reads the password from the secrets file.

Deploying a new Domino server on Docker
To deploy a new Domino server in a Docker container, complete the following steps.

Upgrading a containerized Domino server
Upgrading a containerized Domino server is very similar to upgrading a non-containerized server, except that instead of installing a new version, the existing container is stopped and removed, and the existing data volume is used to create a new container using an updated Domino container image. Starting the container the first time with a new image takes care of applying templates to the existing data volume.

Useful Docker commands
Following are descriptions of some Docker commands that are useful for interacting with containers.

Running Domino-related commands inside the container

Help on Help

All Help Contents

Help on Help