Docker containers

Create
Docker®
 images with
FactoryTalk Optix Applications
 and then run these applications in
Docker
 containers.
IMPORTANT:
Rockwell Automation
 is not responsible for any third-party software, including but not limited to its performance, security, updates, or compatibility with our products. Any use of third-party software is at your own risk, and we do not provide support, warranties, or guarantees for such software. Users should refer to the respective third-party providers for assistance and licensing terms.

This section includes

  • Container-based deployment and host requirements.
  • Licensing methods, runtime limits, and container limitations.
  • Creating a Docker image for an application.
  • Running containers with online entitlements.
  • Running containers with offline entitlements.
  • Docker run parameters.
  • Troubleshooting startup, licensing, and runtime issues.

Overview

Docker®
 deployment packages a
FactoryTalk Optix Application
 and its Linux runtime environment into an image. This approach helps you run the same application in a consistent container environment. It also supports deployment and update scenarios for container-based systems.

Requirements

To use
Docker
 containers, install
Docker
 and use tools that support Linux x86 64 container images and Dockerfiles. Build the image from a compatible exported application, and run the container on a host that supports the same container image.

Licensing and limitations

Continuous runtime requires a valid license. Without a valid license, the application stops after 120 minutes. Online licensing validates the license while the container runs and requires internet connectivity. Offline licensing validates the license without internet connectivity and suits isolated or restricted networks.
Select the licensing method that matches the deployment environment. Online licensing fits connected systems that keep access to the licensing service. Offline licensing fits systems that block external network access or require local license validation.
  • Containers do not support the native presentation engine. Use a web presentation engine if the application requires a graphical interface.
  • The deployment and update service uses port 49100. Map external port 49100 to internal port 49100. Do not map this service to a different external port.
  • Use an automatic restart policy so the container restarts after a failure.
For more information about licensing and activation, see FactoryTalk Optix Installation Guide.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal