5.4. Embedding a container
You can customize your blueprint to embed the latest RHEL container. The containers list contains objects with a source, and optionally, the tls-verify attribute.
The container list entries describe the container images to be embedded into the image.
-
source- Mandatory field. Reference to the container image at a registry. This example uses theregistry.access.redhat.comregistry. You can specify a tag version. The default tag version is the latest. -
name- The name of the container in the local registry. -
tls-verify- Boolean field. The tls-verify boolean field controls the Transport Layer Security. The default value is true.
The embedded containers do not start automatically. To start it, create systemd unit files or quadlets with the file customization.
Prerequisites
- You have created a blueprint.
Procedure
To embed a container from
registry.access.redhat.com/ubi10/ubi:latestand a container from your host, add the following customization to your blueprint:[[containers]] source = "registry.access.redhat.com/ubi10/ubi:latest" name = local_name tls-verify = true [[containers]] source = "localhost/test:latest" local-storage = trueYou can access protected container resources by using a
containers-auth.jsonfile. See Container registry credentials.