public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, quirin.gylstorff@siemens.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [RFC v2 15/19] ddi image: convert to two stage deploy
Date: Fri, 20 Feb 2026 18:15:57 +0100	[thread overview]
Message-ID: <20260220171601.3845113-16-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20260220171601.3845113-1-felix.moessbauer@siemens.com>

By that it is compatible with the unshare chroot mode.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/classes-recipe/imagetypes_ddi.bbclass | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/meta/classes-recipe/imagetypes_ddi.bbclass b/meta/classes-recipe/imagetypes_ddi.bbclass
index 0e45fb8a..7ffd24db 100644
--- a/meta/classes-recipe/imagetypes_ddi.bbclass
+++ b/meta/classes-recipe/imagetypes_ddi.bbclass
@@ -11,13 +11,12 @@ DDI_SIGNING_KEY_PATH ?= ""
 DDI_SIGNING_CERTIFICATE_PATH ?= ""
 DDI_TYPE ?= "sysext"
 DDI_DEFINITION_PATH ?= "/usr/share/isar-ddi-definitions/${DDI_TYPE}.repart.d"
-DDI_OUTPUT_IMAGE ?= "${IMAGE_FULLNAME}.ddi"
 
 ddi_not_supported() {
     bberror "IMAGE TYPE DDI is not supported in distribution Release '${BASE_DISTRO_CODENAME}'"
 }
 
-create_ddi_image() {
+IMAGE_CMD:ddi() {
   local_extra_arguments=""
   if [ -n "${DDI_SIGNING_KEY_PATH}" ]; then
     local_extra_arguments="${local_extra_arguments} --private-key=${DDI_SIGNING_KEY_PATH}"
@@ -26,7 +25,7 @@ create_ddi_image() {
     local_extra_arguments="${local_extra_arguments} --certificate=${DDI_SIGNING_CERTIFICATE_PATH}"
   fi
 
-  rm -rf ${DEPLOY_DIR_IMAGE}/${DDI_OUTPUT_IMAGE}
+  rm -f ${IMAGE_FILE_HOST}
 
   ${SUDO_CHROOT} << EOF
     if [ -z ${DDI_SIGNING_KEY_PATH} ]; then
@@ -37,11 +36,10 @@ create_ddi_image() {
       --copy-source=${PP_ROOTFS} \
       --empty=create --size=auto --dry-run=no  \
       --no-pager $local_extra_arguments \
-      ${PP_DEPLOY}/${DDI_OUTPUT_IMAGE}
+      ${IMAGE_STAGE_CHROOT}
 EOF
 }
 
 IMAGE_CMD:ddi:buster = "ddi_not_supported"
 IMAGE_CMD:ddi:bullseye = "ddi_not_supported"
 IMAGE_CMD:ddi:bookworm = "ddi_not_supported"
-IMAGE_CMD:ddi = "create_ddi_image"
-- 
2.51.0

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20260220171601.3845113-16-felix.moessbauer%40siemens.com.

  parent reply	other threads:[~2026-02-20 17:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 17:15 [RFC v2 00/20] add support to build isar unprivileged 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 01/19] refactor bootstrap: store rootfs tar with user permissions 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 02/19] deb-dl-dir: export without root privileges 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 03/19] download debs without locking 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 04/19] introduce wrappers for privileged execution 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 05/19] bootstrap: move cleanup trap to function 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 06/19] rootfs: rework sstate caching of rootfs artifact 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 07/19] rootfs_generate_initramfs: rework deployment to avoid chowning 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 08/19] wic: rework image deploy logic to deploy under correct user 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 09/19] use bitbake function to generate mounting scripts 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 10/19] apt-fetcher: prepare for chroot specific fetching 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 11/19] add support for fully rootless builds 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 12/19] add helper script to clean artifacts in build dir 'Felix Moessbauer' via isar-users
2026-02-20 18:24   ` 'Jan Kiszka' via isar-users
2026-02-20 17:15 ` [RFC v2 13/19] apt-fetcher: implement support for unshare backend 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 14/19] vm images: make compatible with rootless build 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` 'Felix Moessbauer' via isar-users [this message]
2026-02-20 17:15 ` [RFC v2 16/19] container " 'Felix Moessbauer' via isar-users
2026-02-20 17:15 ` [RFC v2 17/19] dpkg-source: implement multiarch support for unshare backend 'Felix Moessbauer' via isar-users
2026-02-20 17:16 ` [RFC v2 18/19] rootfs: remove temporary sstate deploy directory after task execution 'Felix Moessbauer' via isar-users
2026-02-20 17:16 ` [RFC v2 19/19] use copy of sbom-chroot for sbom creation 'Felix Moessbauer' via isar-users
2026-02-24 10:33   ` Uladzimir Bely
2026-02-24 11:36     ` 'MOESSBAUER, Felix' via isar-users
2026-02-24 11:59       ` Uladzimir Bely
2026-02-24 12:28         ` 'MOESSBAUER, Felix' via isar-users
2026-02-20 17:24 ` [RFC v2 00/20] add support to build isar unprivileged 'Jan Kiszka' via isar-users

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=20260220171601.3845113-16-felix.moessbauer@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@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