Index
Build and customize AutoSD images¶
When you need a production-ready OS image tailored to your requirements, the AutoSD build system provides a declarative, manifest-driven workflow. This section covers everything from creating your first custom image to securing, optimizing, and distributing it.
The image-building process centers on four main areas:
- 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.
All AutoSD images include SELinux in enforcing mode by default. For applications that need fine-grained access control across partition boundaries, you can create custom SELinux policies. For details, see Understanding SELinux policies in AutoSD images.
This section also covers system configuration (users, networking, schedulers, memory allocation), image security (encryption, SELinux, secure boot), performance optimization, and advanced build options. Use the navigation menu to explore these topics.
Next steps¶
After building your image, flash it onto your target hardware. See Provision and maintain for platform-specific flashing guides.
Important
--8<-- "docs/fusa_disclaimer.md"