第13章 Pushing a container to a registry and embedding it into an image
With RHEL image builder, you can build security-hardened images by using the OpenSCAP tool. You can take advantage of the support for container customization in the blueprints to create a container and embed it directly into the image you create.
13.1. Customizing a blueprint to embed a container into an image リンクのコピーリンクがクリップボードにコピーされました!
Embed a container from registry.access.redhat.com by adding a container customization to your blueprint. RHEL image builder pulls the container during the image build and stores the container in the image.
The default local container storage location depends on the image type, so that all supported container-tools, such as Podman, can work with it.
Prerequisites
- You have created a blueprint.
Procedure
- Customize your blueprint with the container:
[[containers]]
source = "registry.access.redhat.com/ubi10/ubi:latest"
name = "_<local_name>_"
tls-verify = true
-
source- Mandatory field. It is a 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 thelatest. -
name- The name of the container in the local registry. tls-verify- Boolean field. Thetls-verifyboolean field controls the transport layer security. The default value istrue.To access protected container resources, you can use a
containers-auth.jsonfile.