Go To Top

Return to Risks and Open Decisions

The team must decide which container runtime Phase 0 uses and which alternatives, if any, it supports. The container runtime affects build commands, networking, volume mounts, logs, cleanup, DDS discovery, and CI or demonstration execution.

Open container decisions may include:

1. Whether Docker, Docker Compose, Podman, or another runtime acts as the primary baseline.
2. Which version range the team supports.
3. Whether developer workstations and CI runners use the same runtime.
4. Whether the team uses one container per Node or groups multiple support functions in a container.
5. How containers expose logs and Evidence.
6. How container networking supports DDS discovery and communication.
7. Which cleanup behavior the team permits.

Container runtime decisions should appear in the applicable checklist instance. If the team supports multiple runtimes, each runtime should have its own product entry, version range, validation method, and known constraints.