oci-layer-composition

BuildStream assembles OCI images by passing packages through stack, compose, and script elements to layer and filter artifacts. This process defines the parent layer hierarchy and applies junction overrides to control the final image contents.

Missing packages in an OCI image layer often result from incorrect split domain filtering during the compose stage. You must trace the package path through the stack and compose elements to identify where the files are excluded.

The prepare-image.sh and build-oci scripts execute specific preparation and build tasks during OCI image composition. They process the assembled file artifacts and apply the necessary configurations before the final image layer is generated.

Common mistakes in split domain management for OCI construction include incorrectly mapping package domains or failing to apply junction overrides. These errors prevent files from being properly included in the composed image layers.

Debugging missing files in a built OCI container image requires tracing the artifact flow through the composition stages. You need to inspect the stack and compose elements to verify that split domain filtering includes the intended files.

Junction overrides are needed in BuildStream OCI assembly when you must alter the default parent layer hierarchy or replace specific project dependencies. They ensure the composition stage pulls the correct artifact versions for the image.