14.5 Container Networking [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 14.5 Container Networking ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:14-containerisation:start | Return to Containerisation ]]

Container networking should support [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] discovery, topic communication, Node observation, and test execution. The team should document the networking assumptions that affect Phase 0 runtime behavior.

Container networking documentation should identify:

  - Required container networks.
  - DDS domain Configuration.
  - Discovery assumptions.
  - Host-to-container communication requirements.
  - Container-to-container communication requirements.
  - Exposed ports, where applicable.
  - Multicast requirements, where applicable.
  - Network constraints for developer workstations, CI runners, and demonstration environments.
  - Any DDS-vendor-specific networking requirements.

DDS networking can behave differently across host operating systems, container runtimes, and DDS vendors. The applicable tool Baseline checklist instance should identify the supported container runtime, operating-system assumptions, DDS product, and any known networking constraints.

The team should validate container networking as part of acceptance when the Node network runs in containers. Validation should confirm that required Nodes can discover one another, publish and subscribe to required topics, and report [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] status.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>