Sentinel RMS Licensing in Docker Containers

This section describes the Sentinel RMS-licensed applications tested on Docker containers.

General Requirements

The assumptions for Sentinel RMS-based licensing in Docker containers are:

For more information...

To learn about how to build docker images with License Managers, refer to Knowledge Base article KB0028016 in the Customer Support Portal.

>All the necessary redistributable components need to be bundled together. For example, the license, License Manager (service), and SCP service (if required) must be located in a single location.

>You need to ensure the following when the Docker container is launched:

The persistence needs to be set up for standalone deployments else the licensed applications using persistence-based data models will not work. After the container's restart, all persistence-based data models data will be lost.

The license needs to be installed.

>The docker volume is volatile. This volatility will affect the RMS persistence folders, usage folder, license, and trace files. To counter the volatility, Thales suggests mounting these folders from a source outside of the container (generally any folder to be mapped to the original folders). Set up the mounting so that the data is consistent during restarts.

Docker Images Tested

Operating System

Images
Windows

>mcr.microsoft.com/windows:ltsc2019

>mcr.microsoft.com/windows/servercore:ltsc2019

Linux

>debian:11.6

>ubuntu:22:04

>opensuse/leap:15.4

>redhat/ubi9

>registry.suse.com/suse/sle15:15.4.27.11.31

Limitations

All the licensing attributes listed under the Flexible License Model for each deployment mode are supported with the following limitations:

Windows

The following licensing features are not supported:

>Locking: Hard Disk Serial (0x800) and Ethernet Address (0x010)

>Remote session detection

Linux

The following licensing features are not supported:

>Locking: Hard Disk Serial (0x800) and UUID (0x2000)

>Remote session detection

>VM detection