Embedding containerized applications in the QM partition¶
Place all QM-level containerized applications in the QM partition. When you write your automotive image builder manifest, place all
QM-specific operations inside the qm
stage.
To configure your custom automotive image builder manifest to install one or more container images in the QM partition, include the
qm
stage in your manifest file. Create a content
section in the the qm
stage and define the source URL, tag, and name of the
container image.
You can view a complete example manifest for QM container configuration in the demos/container_qm/container_qm.aib.yml file.
Prerequisites
-
One or more container images available from a local or remote registry.
Note
Installing container images from local storage is appropriate only for development and experimental purposes.
Procedure
-
Include the
qm
stage in your manifest to initialize the QM partition. Addcontent
andcontainer_images
sections to theqm
stage so that you can define the container images that you want to install:automotive image builder manifestqm: content: container_images: # Get the CS10 base container in from a local container registry - source: quay.io/centos/centos tag: stream10 name: localhost/cs10 containers-transport: containers-storage # Get the auto-apps container image from a remote container registry # here gitlab - source: registry.gitlab.com/centos/automotive/sample-images/demo/auto-apps tag: latest name: localhost/auto-apps
Note
To install a container image from local storage, set the
containers-transport: containers-storage
parameter. -
Optional. If you have container configuration files that you want to copy to the image, use the
add_files
section within thecontent
stage. For example, copy the exampleradio.container
andengine.container
files to the image:automotive image builder manifestadd_files: - path: /etc/containers/systemd/radio.container source_path: ../radio.container - path: /etc/containers/systemd/engine.container source_path: ../engine.container
Note
The
source_path:
option resolves a relative path. In this example, the container configuration files are in the../demos
directory.
Next steps
Now that you have included your containerized application in your automotive image builder manifest, you can build your AutoSD image. For more information, see Building an image from a custom manifest.