18.7 Container Acceptance Criteria [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.

====== 18.7 Container Acceptance Criteria ======

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

[[fxdemo:05-part:18-acceptance-criteria:start | Return to Acceptance Criteria ]]

Containerization satisfies Phase 0 acceptance when the team can build, run, inspect, stop, and clean up the required containers using documented scripts and configuration.

Container acceptance requires:

  - Container definitions exist in the approved Repository location.
  - Container builds use controlled Repository inputs.
  - Container builds do not depend on undocumented local files.
  - Container images follow the approved naming convention.
  - Container runtime configuration uses approved configuration files, environment variables, mounted volumes, command-line arguments, or orchestration settings.
  - Containers do not embed secrets, credentials, personal paths, or machine-specific assumptions.
  - Required containers start through the approved run scripts.
  - Required containers expose logs through the documented mechanism.
  - Required [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] running in containers can participate in expected DDS communication.
  - Required containers stop through the approved stop script.
  - Cleanup actions do not destroy logs or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] unless the user explicitly requests destructive cleanup.
  - Container build, run, stop, and cleanup Evidence is available where acceptance requires it.

----

<WRAP centeralign>

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

</WRAP>