14.6 Container Naming [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.6 Container Naming ======

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

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

Container names and image names should follow the naming conventions defined in Section 7.9. The names should identify the project, phase, [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] or support service, and, where useful, the runtime role.

A representative image naming pattern is:

  - fsa-phase0-<node-or-service>

Representative examples include:

  - fsa-phase0-fx-validation-node
  - fsa-phase0-control-plane-observer
  - fsa-phase0-dds-tools

Runtime container names may use an instance suffix when more than one instance can run:

  - fsa-phase0-fx-validation-node-1
  - fsa-phase0-control-plane-observer-1

Container names should not replace Node names. The Node name identifies the architectural runtime participant. The container name identifies the packaging and execution unit. The implementation may map one Node to one container in Phase 0, but the documentation should preserve the distinction.

----

<WRAP centeralign>

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

</WRAP>