Embedding RPM application packages in the QM partition¶

The AutoSD architecture isolates non-critical (QM) applications from critical applications. This isolation mechanism is the QM software partition. In this architecture, the QM partition is an imageless container that uses a subsection of the host filesystem as its root filesystem.

QM-level RPM application packages belong in the QM partition. When you create an Automotive Image Builder manifest, place all QM-specific operations inside the qm stage.

Prerequisites

A QM-level RPM package that you want to install. For example, the auto-apps RPM that you created in Packaging sample applications with RPM, or any RPM package available from a remote repository.
A custom manifest file, such as the file that you created in Embedding RPM packages from local storage into the AutoSD image

Procedure

To configure your custom automotive image builder manifest to install your auto-apps application into the QM partition of the OS image, include the qm stage in your manifest file. Create a content section in the the qm stage and define the repository that you want to enable, as well as the RPM that you want to install:
automotive image builder manifest
```
qm:
  content:
    repos:
      - id: auto-apps
        baseurl: file:///var/tmp/my_repo
    rpms:
      - auto-apps
```

Next steps

Now that you have configured your custom automotive image builder manifest to initialize the QM partition and install your RPM package, you can build your AutoSD image. For more information, see Building an image from a custom manifest.