20.4 Container Runtime Decisions [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.

===== 20.4 Container Runtime Decisions =====

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

[[fxdemo:05-part:20-risks-and-open-decisions:start | 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:

  - Whether Docker, Docker Compose, Podman, or another runtime acts as the primary baseline.
  - Which version range the team supports.
  - Whether developer workstations and CI runners use the same runtime.
  - Whether the team uses one container per [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] or groups multiple support functions in a container.
  - How containers expose logs and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].
  - How container networking supports DDS discovery and communication.
  - 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.

----

<WRAP centeralign>

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

</WRAP>