From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>,
Henning Schild <henning.schild@siemens.com>
Subject: [PATCH 3/4] classes: allow more control over container image name and tag
Date: Wed, 28 Jul 2021 17:22:09 +0200 [thread overview]
Message-ID: <20210728152210.7089-4-henning.schild@siemens.com> (raw)
In-Reply-To: <20210728152210.7089-1-henning.schild@siemens.com>
This patch allows more fine-grained control over how the resulting
container will be tagged. Where the default name will be PN together
with DISTRO and ARCH, and tag will be derived from PV and PR
Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
meta/classes/container-img.bbclass | 4 +---
meta/classes/image-container-extension.bbclass | 11 ++++++-----
meta/classes/image-sdk-extension.bbclass | 2 +-
3 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/meta/classes/container-img.bbclass b/meta/classes/container-img.bbclass
index 79ef3e8d756b..9928a58ef53d 100644
--- a/meta/classes/container-img.bbclass
+++ b/meta/classes/container-img.bbclass
@@ -9,10 +9,8 @@
do_container_image[stamp-extra-info] = "${DISTRO}-${MACHINE}"
do_container_image[vardeps] += "CONTAINER_FORMATS"
do_container_image(){
- rootfs_id="${DISTRO}-${DISTRO_ARCH}"
-
bbdebug 1 "Generate container image in these formats: ${CONTAINER_FORMATS}"
- containerize_rootfs "${IMAGE_ROOTFS}" "${rootfs_id}" "${CONTAINER_FORMATS}"
+ containerize_rootfs "${IMAGE_ROOTFS}" "${CONTAINER_FORMATS}"
}
addtask container_image before do_image after do_image_tools
diff --git a/meta/classes/image-container-extension.bbclass b/meta/classes/image-container-extension.bbclass
index 0e70ba9c1405..43b67f9d864d 100644
--- a/meta/classes/image-container-extension.bbclass
+++ b/meta/classes/image-container-extension.bbclass
@@ -6,15 +6,16 @@
# This class extends the image.bbclass for containerizing the root filesystem.
CONTAINER_FORMATS ?= "docker-archive"
+CONTAINER_IMAGE_NAME ?= "${PN}-${DISTRO}-${DISTRO_ARCH}"
+CONTAINER_TAG ?= "${PV}-${PR}"
containerize_rootfs() {
local cmd="/bin/dash"
local empty_tag="empty"
- local tag="latest"
+ local tag="${CONTAINER_TAG}"
local oci_img_dir="${WORKDIR}/oci-image"
local rootfs="$1"
- local rootfs_id="$2"
- local container_formats="$3"
+ local container_formats="$2"
# prepare OCI container image skeleton
bbdebug 1 "prepare OCI container image skeleton"
@@ -42,9 +43,9 @@ containerize_rootfs() {
sudo chown --recursive $(id -u):$(id -g) "${oci_img_dir}"
# convert the OCI container image to the desired format
- image_name="isar-${rootfs_id}"
+ image_name="${CONTAINER_IMAGE_NAME}"
for image_type in ${CONTAINER_FORMATS} ; do
- image_archive="${DEPLOY_DIR_IMAGE}/${rootfs_id}-${image_type}.tar"
+ image_archive="${DEPLOY_DIR_IMAGE}/${image_name}-${tag}-${image_type}.tar"
bbdebug 1 "Creating container image type: ${image_type}"
case "${image_type}" in
"docker-archive" | "oci-archive")
diff --git a/meta/classes/image-sdk-extension.bbclass b/meta/classes/image-sdk-extension.bbclass
index 426b92595554..fa15b588068c 100644
--- a/meta/classes/image-sdk-extension.bbclass
+++ b/meta/classes/image-sdk-extension.bbclass
@@ -80,7 +80,7 @@ do_populate_sdk() {
# generate the SDK in all the desired container formats
if [ -n "${sdk_container_formats}" ] ; then
bbnote "Generating SDK container in ${sdk_container_formats} format"
- containerize_rootfs "${SDKCHROOT_DIR}" "sdk-${DISTRO}-${DISTRO_ARCH}" "${sdk_container_formats}"
+ containerize_rootfs "${SDKCHROOT_DIR}" "${sdk_container_formats}"
fi
}
--
2.31.1
next prev parent reply other threads:[~2021-07-28 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 15:22 [PATCH 0/4] Allow better control over container tags Henning Schild
2021-07-28 15:22 ` [PATCH 1/4] classes: make sure container extension can run multiple times Henning Schild
2021-07-29 8:29 ` Silvano Cirujano Cuesta
2021-07-28 15:22 ` [PATCH 2/4] classes: simplify tag handling in container class Henning Schild
2021-07-29 8:49 ` Silvano Cirujano Cuesta
2021-07-28 15:22 ` Henning Schild [this message]
2021-07-29 12:50 ` [PATCH 3/4] classes: allow more control over container image name and tag Silvano Cirujano Cuesta
2021-07-29 13:05 ` Henning Schild
2021-07-29 13:13 ` Silvano Cirujano Cuesta
2021-07-28 15:22 ` [PATCH 4/4] classes: fix comment in container-img class Henning Schild
2021-07-29 12:52 ` Silvano Cirujano Cuesta
2021-07-28 15:23 ` [PATCH 0/4] Allow better control over container tags Henning Schild
2021-07-29 12:58 ` Silvano Cirujano Cuesta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210728152210.7089-4-henning.schild@siemens.com \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=silvano.cirujano-cuesta@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox