Docker runtime entitlements

FactoryTalk® Optix™ Runtime

supports entitlement handling for Docker container deployments on Ubuntu 22.04. This entitlement context applies to Runtime instances that run inside Docker containers.

Docker runtime deployments support online and offline entitlement models. The deployment model determines whether the container validates an entitlement through entitlement web services or uses an offline entitlement value from a host with an activated entitlement.

In online deployments, the container uses an entitlement serial number in the

FTOPTIX_ENTITLEMENT_SERIAL_NUMBER

environment variable. This value triggers the Call Home entitlement mechanism for the running container. For more information, see Call Home entitlement mechanism.

The Docker entitlement context links a running container to a valid Runtime entitlement.

In online deployments, the container communicates with entitlement web services to lock the specified entitlement.

The container refreshes the entitlement lock at regular intervals and unlocks the entitlement when Runtime stops normally.

If the entitlement web service connection fails after the entitlement lock succeeds, a seven-day grace period starts.

In offline deployments, the entitlement is activated on the host, and the container uses the matching offline entitlement value at startup. This model supports systems that do not keep a connection to entitlement web services.

Docker deployments require a valid entitlement for continuous runtime. Without a valid entitlement, the application stops after 120 minutes.

Use the online entitlement model for connected systems. Use the offline entitlement model when the host does not keep internet access.

Use this entitlement context only for Runtime deployments that run in Docker containers. Containers do not support the native presentation engine. Use a web presentation engine if the application requires a graphical interface.