Skip to content

Docker containers and swarm network (v3 before 3.3)

This page explains the role of Docker in KX Sensors v3 releases before 3.3, where RT sequencers run as containers, and important caveats when upgrading RT.

Applies to KX Sensors v3 releases before 3.3 only

As of KX Sensors 3.3, RT processes run directly on the host and Docker is no longer a prerequisite. If you're running 3.3 or later, see How RT processes run instead. This page is retained for deployments still on an earlier v3 release.

  • For portability across operating systems, RT sequencers are deployed as Docker containers.
  • Docker is a prerequisite of KX Sensors v3 releases before 3.3 and is installed as part of our installation scripts.
  • The core KX Sensors package includes a container image encapsulating the RT sequencer implementation.
  • KX Sensors upgrades in which the version of RT changes require an additional procedure. See RT upgrades.
  • Running docker ps will show running containers in an active KX Sensors system. Docker commands can also be used to stop and start containers; however, this is the responsibility of the RT Orchestrator (RTO) instance on each node.
  • In addition to installing Docker, installing KX Sensors also creates a Docker swarm overlay network. The overlay network is used exclusively by RT containers to communicate across physical hosts. RT container port requirements and the use of Docker DNS to resolve other containers by hostname necessitate the use of a Docker swarm overlay network.

Next steps