7.9 Container Naming

Go To Top

Return to Naming and File Conventions

Container names should identify the project, phase, Node or service, and where useful, the runtime role. The naming convention should help developers inspect running containers, logs, networks, and images without having to guess which process belongs to which Node.

A representative container 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 follow the same pattern with an environment or instance suffix if needed:

• 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. In simple Phase 0 cases, one container may run one Node, but the team should still preserve the distinction between logical Node identity and container runtime identity.

The team should keep container naming consistent across container definitions, build scripts, run scripts, logs, documentation, and acceptance Evidence. A reviewer should be able to trace a container image or running container back to the Node or support service it packages.