18.7 Container Acceptance Criteria

Go To Top

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:

1. Container definitions exist in the approved Repository location.
2. Container builds use controlled Repository inputs.
3. Container builds do not depend on undocumented local files.
4. Container images follow the approved naming convention.
5. Container runtime configuration uses approved configuration files, environment variables, mounted volumes, command-line arguments, or orchestration settings.
6. Containers do not embed secrets, credentials, personal paths, or machine-specific assumptions.
7. Required containers start through the approved run scripts.
8. Required containers expose logs through the documented mechanism.
9. Required Nodes running in containers can participate in expected DDS communication.
10. Required containers stop through the approved stop script.
11. Cleanup actions do not destroy logs or Evidence unless the user explicitly requests destructive cleanup.
12. Container build, run, stop, and cleanup Evidence is available where acceptance requires it.