14.3 Container Build Inputs [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.

====== 14.3 Container Build Inputs ======

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

[[fxdemo:05-part:14-containerisation:start | Return to Containerisation ]]

Container builds should use controlled [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] inputs. The ''buildContainers.sh'' script should validate the required inputs before it builds images.

Container build inputs may include:

  - Container definition files.
  - Handwritten source files.
  - Generated [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]]/[[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] Artifacts.
  - Runtime Configuration templates.
  - Build scripts.
  - Dependency manifests.
  - Package manager Configuration.
  - Node startup commands.
  - Supporting tools required inside the image.
  - Documentation or metadata files required for runtime inspection.

Container builds should not depend on untracked local files. If a build requires a file that is not in the Repository, the handbook, checklist instance, or build documentation should identify the source and explain how the build obtains or validates it.

The team should treat generated Artifacts carefully. If the build uses generated DDS bindings, the build process should either generate them before the container build or verify that approved generated outputs already exist. The build should fail clearly when the required generated Artifacts are missing or stale.

----

<WRAP centeralign>

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

</WRAP>