Home
Installing
Domino Leap on Docker
The following topics contain information on how to successfully deploy an HCL Domino Leap server using a Docker-compatible Red Hat Universal Base Image (UBI).
Deploying a new Domino Leap server on Docker
Completing the Domino Leap server configuration
After your Domino Leap server starts, use your Notes or Domino Administrator client to complete the server configuration.

Installing
- Domino Leap on Docker
  The following topics contain information on how to successfully deploy an HCL Domino Leap server using a Docker-compatible Red Hat Universal Base Image (UBI).
  - Domino Leap on Docker overview
    HCL Domino Leap 1.1 includes a Docker-compatible Red Hat Universal Base Image (UBI) of Domino Leap that is part of your entitlement and available for download through the HCL Licensing Portal. HCL Domino Leap is pre-installed on this image – this allows you to deploy a Domino Leap server as a container with just a few commands.
  - Loading the Domino Leap tar archive file to Docker
    The first step to deploy a Domino Leap server on Docker is loading the dleap-container tar archive file to Docker. This creates the image that is used to create containers.
  - Upgrading a containerized Domino Leap server
  - Deploying a new Domino Leap server on Docker
    - Creating the Docker volume to store the data directory
      After you load the dleap-container image to Docker, create a Docker volume. The Docker volume is a persistent location to hold the Domino data directory.
    - Creating a Docker container for Domino Leap
      Domino Leap 1.1 on Docker is a Domino on Docker server that has Domino Leap installed.
    - Completing the Domino Leap server configuration
      After your Domino Leap server starts, use your Notes or Domino Administrator client to complete the server configuration.
  - Deploying a sample Domino Leap server on Docker
    The sample Domino Leap 1.1 server (Dleap/Renovations) is pre-configured for Leap 1.1.
- Installing Domino Leap
  The following topics contain information on how to successfully install HCL Domino Leap.
- Uninstalling Domino Leap on Linux
  To uninstall Domino Leap on a Domino server running on a Linux operating system, complete the following steps.
- Configuring a proxy for Domino Leap High Availability

Completing the Domino Leap server configuration

After your Domino Leap server starts, use your Notes or Domino Administrator client to complete the server configuration.

Note: The Domino Leap Docker container publishes the NRPC (1352) port to the host system running Docker. Before you complete the following steps, create a connection record to the Domino Leap server in your Notes or Domino Administrator local address book.

Procedure

Enable the HTTP GET, POST, PUT, DELETE and HEAD methods as described in Configuring the server.
Enable session authentication as described in Configuring the server. Domino Leap works best when at least “Single Server” authentication is enabled, but other forms of session authentication are supported. Basic authentication is not recommended.
Modify the serverURI setting as described in the "Verify VoltConfig.nsf" section in Post-installation tasks. The serverURI hostname, protocol and port must match the parameters in the docker run command.
Restart the Domino HTTP process to be sure each of the preceding changes take effect.
Launch a browser and visit the Domino Leap Manager page.

Results

The Domino Leap server is completely configured and ready to use. The absolute URL of the Domino Leap manager page depends on your server host name and whether you have enabled HTTPS on your server. The relative URL is /volt-apps/secure/org/ide/manager.html. For example, if the container host name is docker.renovations.com, the absolute URL might be http://docker.renovations.com/volt-apps/secure/org/ide/manager.html.

Note: Users can create a bash session in their Domino Leap container to modify configuration files such as notes.ini using the docker exec command. For example: docker exec -u notes -it volt /bin/bash provides an interactive bash shell with "notes" user access that can be used to modify /local/notesdata/notes.ini.