16.6 Container Errors

Go To Top

Return to Exception Handling

Containers should remain visible to developers, testers, reviewers, and demonstration operators. Container startup, runtime, networking, logging, and shutdown failures should not disappear inside the container runtime.

Container error handling should identify:

1. Image build failure.
2. Missing build inputs.
3. Missing generated Artifacts.
4. Invalid runtime Configuration.
5. Missing mounted files or volumes.
6. Container networking failure.
7. DDS discovery failure inside the container environment.
8. Process startup failure.
9. Process termination or crash.
10. Log export failure.
11. Controlled shutdown failure.
12. Cleanup failure.

The build and run scripts should report container errors clearly. Container logs should preserve Node or service errors where practical. If a container fails to start a required Node, the run script should report failure and return a non-zero exit code.

Container cleanup should not delete logs or Evidence needed to diagnose a failure unless the user explicitly requests destructive cleanup.