Building a custom AutoSD image¶
The AutoSD image-building process centers on three main components:
- Custom manifests – YAML files that define the content and configuration of an OS image
- Automotive Image Builder – the tool that resolves dependencies, assembles packages, and produces the final image
- Bootc container images – the default build artifact, packaging the full OS into a standard OCI container that supports over-the-air updates
- Bootc image layering – customize a base bootc image by adding packages, files, and configuration through standard container build techniques
Automotive Image Builder produces bootc container images by default using
aib build. You can then convert the container image to a flashable disk
image with aib to-disk-image, or combine both steps into a single
command. For step-by-step instructions, see
Building bootc images.
You can also layer additional packages and configuration on top of a
base bootc image using standard Containerfile techniques. For details,
see Bootc image layering.
A package-based build path is also available through aib-dev build for
development and testing workflows that produce disk images directly.
After building an image, you can push it to a container registry and update running systems over the air. For details, see Registry interactions.
Important
AutoSD is the public preview of the Red Hat In-Vehicle Operating System (RHIVOS) product and contains all of the technology and tools necessary to run a mixed-criticality workload on that safety certified product. The documentation on this page presents the technology underlying and available in the product, but all safety requirements and documents are not covered here and are available only to RHIVOS customers. These safety documents impose some limitations and additional activities necessary for safety workloads.