From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "quirin.gylstorff@siemens.com" <quirin.gylstorff@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"wzh@ilbers.de" <wzh@ilbers.de>
Subject: Re: [PATCH v4 04/10] meta: add SBOM generation with debsbom
Date: Mon, 24 Nov 2025 09:16:41 +0000 [thread overview]
Message-ID: <245b4cc8328aaccca63ab7a52be6926ffa8614d5.camel@siemens.com> (raw)
In-Reply-To: <0e93fd0b-d55f-4ab6-9d77-b3e565ff15cb@siemens.com>
On Thu, 2025-11-20 at 12:07 +0100, Quirin Gylstorff wrote:
> On 11/19/25 17:58, Zhihang Wei wrote:
> >
> > On 11/19/25 16:54, 'Quirin Gylstorff' via isar-users wrote:
> > >
> > >
> > > On 11/17/25 14:24, 'Felix Moessbauer' via isar-users wrote:
> > > > From: Christoph Steiger <christoph.steiger@siemens.com>
> > > >
> > > > Generate SBOMs for every rootfs that is created. These SBOMs are placed
> > > > in the image deploy directory.
> > > >
> > > > For the generation a small chroot with debsbom installed is created and
> > > > from that the rootfs of the image is scanned.
> > > >
> > > > The sbom generation is bound to the rootfs feature `generate-sbom`
> > > > which is activated per default now.
> > > >
> > > > Signed-off-by: Christoph Steiger <christoph.steiger@siemens.com>
> > > > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > > > ---
> > > > meta/classes/image.bbclass | 1 +
> > > > meta/classes/initramfs.bbclass | 3 +-
> > > > meta/classes/rootfs.bbclass | 14 +++-
> > > > meta/classes/sbom.bbclass | 64 +++++++++++++++++++
> > > > meta/classes/sdk.bbclass | 2 +-
> > > > .../sbom-chroot/sbom-chroot.bb | 30 +++++++++
> > > > 6 files changed, 111 insertions(+), 3 deletions(-)
> > > > create mode 100644 meta/classes/sbom.bbclass
> > > > create mode 100644 meta/recipes-devtools/sbom-chroot/sbom-chroot.bb
> > > >
> > > > diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> > > > index 1fa71c17..29324920 100644
> > > > --- a/meta/classes/image.bbclass
> > > > +++ b/meta/classes/image.bbclass
> > > > @@ -99,6 +99,7 @@ ROOTFS_FEATURES += "\
> > > > clean-log-files \
> > > > clean-debconf-cache \
> > > > populate-systemd-preset \
> > > > + generate-sbom \
> > > > "
> > > > ROOTFS_PACKAGES += "${IMAGE_PREINSTALL}
> > > > ${@isar_multiarch_packages('IMAGE_INSTALL', d)}"
> > > > ROOTFS_MANIFEST_DEPLOY_DIR ?= "${DEPLOY_DIR_IMAGE}"
> > > > diff --git a/meta/classes/initramfs.bbclass b/meta/classes/
> > > > initramfs.bbclass
> > > > index 862bd873..570780e1 100644
> > > > --- a/meta/classes/initramfs.bbclass
> > > > +++ b/meta/classes/initramfs.bbclass
> > > > @@ -22,11 +22,12 @@ INITRAMFS_FULLNAME = "${PN}-${DISTRO}-${MACHINE}"
> > > > # Bill-of-material
> > > > ROOTFS_MANIFEST_DEPLOY_DIR = "${DEPLOY_DIR_IMAGE}"
> > > > ROOTFS_PACKAGE_SUFFIX = "${INITRAMFS_FULLNAME}"
> > > > +SBOM_DISTRO_NAME:append = "-initramfs"
> > > > DEPENDS += "${INITRAMFS_INSTALL}"
> > > > ROOTFSDIR = "${INITRAMFS_ROOTFS}"
> > > > -ROOTFS_FEATURES = "generate-manifest"
> > > > +ROOTFS_FEATURES = "generate-manifest generate-sbom"
> > > > ROOTFS_PACKAGES = "${INITRAMFS_GENERATOR_PKG}
> > > > ${INITRAMFS_PREINSTALL} ${INITRAMFS_INSTALL}"
> > > > # validate if have incompatible packages in the installation list
> > > > diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
> > > > index c045bfc0..b3ca9e16 100644
> > > > --- a/meta/classes/rootfs.bbclass
> > > > +++ b/meta/classes/rootfs.bbclass
> > > > @@ -3,6 +3,8 @@
> > > > inherit deb-dl-dir
> > > > +inherit sbom
> > > > +
> > > > ROOTFS_ARCH ?= "${DISTRO_ARCH}"
> > > > ROOTFS_DISTRO ?= "${DISTRO}"
> > > > @@ -28,11 +30,18 @@ INITRD_IMAGE ?= ""
> > > > # available features are:
> > > > # 'clean-package-cache' - delete package cache from rootfs
> > > > # 'generate-manifest' - generate a package manifest of the rootfs
> > > > into ${ROOTFS_MANIFEST_DEPLOY_DIR}
> > > > +# 'generate-sbom' - generate a SBOM of the rootfs into
> > > > ${DEPLOY_DIR_SBOM}
> > > > # 'export-dpkg-status' - exports /var/lib/dpkg/status file to
> > > > ${ROOTFS_DPKGSTATUS_DEPLOY_DIR}
> > > > # 'clean-log-files' - delete log files that are not owned by packages
> > > > # 'populate-systemd-preset' - enable systemd units according to
> > > > systemd presets
> > > > +
> > > > # 'generate-initrd' - generate debian default initrd
> > > > ROOTFS_FEATURES += "${@ 'generate-initrd' if
> > > > d.getVar('INITRD_IMAGE') == '' else ''}"
> > > > +# only supported from bookworm / jammy on
> > > > +ROOTFS_FEATURES:remove:buster = "generate-sbom"
> > > > +ROOTFS_FEATURES:remove:bullseye = "generate-sbom"
> > > > +ROOTFS_FEATURES:remove:jammy = "generate-sbom"
> > > > +ROOTFS_FEATURES:remove:focal = "generate-sbom"
> > > > ROOTFS_APT_ARGS="install --yes -o Debug::pkgProblemResolver=yes"
> > > > @@ -478,6 +487,9 @@ cache_dbg_pkgs() {
> > > > fi
> > > > }
> > > > +# The sbom generator needs the apt-cache, hence run before
> > > > cleaning it
> > > > +ROOTFS_POSTPROCESS_COMMAND +=
> > > > "${@bb.utils.contains('ROOTFS_FEATURES', 'generate-sbom',
> > > > 'do_generate_sbom', '', d)}"
> > > > +
> > > > ROOTFS_POSTPROCESS_COMMAND +=
> > > > "${@bb.utils.contains('ROOTFS_FEATURES', 'clean-package-cache',
> > > > 'rootfs_postprocess_clean_package_cache', '', d)}"
> > > > rootfs_postprocess_clean_package_cache() {
> > > > sudo -E chroot '${ROOTFSDIR}' \
> > > > @@ -647,7 +659,7 @@ python do_rootfs() {
> > > > }
> > > > addtask rootfs before do_build
> > > > -do_rootfs_postprocess[depends] = "base-apt:do_cache isar-
> > > > apt:do_cache_config"
> > > > +do_rootfs_postprocess[depends] = "base-apt:do_cache isar-
> > > > apt:do_cache_config ${@bb.utils.contains('ROOTFS_FEATURES',
> > > > 'generate-sbom', 'sbom-chroot:do_sbomchroot_deploy', '', d)}"
> > > > SSTATETASKS += "do_rootfs_install"
> > > > SSTATECREATEFUNCS += "rootfs_install_sstate_prepare"
> > > > diff --git a/meta/classes/sbom.bbclass b/meta/classes/sbom.bbclass
> > > > new file mode 100644
> > > > index 00000000..fd41296c
> > > > --- /dev/null
> > > > +++ b/meta/classes/sbom.bbclass
> > > > @@ -0,0 +1,64 @@
> > > > +# This software is a part of ISAR.
> > > > +# Copyright (C) 2025 Siemens
> > > > +#
> > > > +# SPDX-License-Identifier: MIT
> > > > +
> > > > +# sbom type to generate, accepted are "cdx" or "spdx"
> > > > +SBOM_TYPES ?= "spdx cdx"
> > > > +
> > > > +SBOM_DEBSBOM_TYPE_ARGS = "${@"-t " + " -t
> > > > ".join(d.getVar("SBOM_TYPES").split())}"
> > > > +
> > > > +# general user variables
> > > > +SBOM_DISTRO_SUPPLIER ?= "ISAR"
> > > > +SBOM_DISTRO_NAME ?= "ISAR-Debian-GNU-Linux"
> > > > +SBOM_DISTRO_VERSION ?= "1"
> > > > +SBOM_DISTRO_SUMMARY ?= "Linux distribution built with ISAR"
> > > > +SBOM_BASE_DISTRO_VENDOR ??= "debian"
> > > > +SBOM_DOCUMENT_UUID ?= ""
> > > > +
> > > > +# SPDX specific user variables
> > > > +SBOM_SPDX_NAMESPACE_PREFIX ?= "https://spdx.org/spdxdocs"
> > > > +
> > > > +DEPLOY_DIR_SBOM = "${DEPLOY_DIR_IMAGE}"
> > > > +
> > > > +SBOM_DIR = "${DEPLOY_DIR}/sbom"
> > > > +SBOM_CHROOT = "${SBOM_DIR}/sbom-chroot"
> > > > +
> > > > +# adapted from the isar-cip-core image_uuid.bbclass
> > > > +def generate_document_uuid(d, warn_not_repr=True):
> > > > + import uuid
> > > > +
> > > > + base_hash = d.getVar("BB_TASKHASH")
> > > > + if base_hash is None:
> > > > + if warn_not_repr:
> > > > + bb.warn("no BB_TASKHASH available, SBOM UUID is not
> > > > reproducible")
> > > > + return uuid.uuid4()
> > > > + return str(uuid.UUID(base_hash[:32], version=4))
> > > > +
> > > > +def sbom_doc_uuid(d):
> > > > + if not d.getVar("SBOM_DOCUMENT_UUID"):
> > > > + d.setVar("SBOM_DOCUMENT_UUID", generate_document_uuid(d))
> > > > +
> > > > +generate_sbom() {
> > > > + sudo mkdir -p ${SBOM_CHROOT}/mnt/rootfs ${SBOM_CHROOT}/mnt/
> > > > deploy-dir
> > > > +
> > > > + TIMESTAMP=$(date --iso-8601=s -d @${SOURCE_DATE_EPOCH})
> > > > + bwrap \
> > > > + --unshare-user \
> > > > + --unshare-pid \
> > > > + --bind ${SBOM_CHROOT} / \
> > > > + --bind ${ROOTFSDIR} /mnt/rootfs \
> > > > + --bind ${DEPLOY_DIR_SBOM} /mnt/deploy-dir \
> > > > + -- debsbom -v generate ${SBOM_DEBSBOM_TYPE_ARGS} -r /mnt/
> > > > rootfs -o /mnt/deploy-dir/'${PN}-${DISTRO}-${MACHINE}' \
> > > > + --distro-name '${SBOM_DISTRO_NAME}' --distro-supplier
> > > > '${SBOM_DISTRO_SUPPLIER}' \
> > > > + --distro-version '${SBOM_DISTRO_VERSION}' --distro-arch
> > > > '${DISTRO_ARCH}' \
> > > > + --base-distro-vendor '${SBOM_BASE_DISTRO_VENDOR}' \
> > > > + --cdx-serialnumber '${SBOM_DOCUMENT_UUID}' \
> > > > + --spdx-namespace
> > > > '${SBOM_SPDX_NAMESPACE_PREFIX}'-'${SBOM_DOCUMENT_UUID}' \
> > > > + --timestamp $TIMESTAMP
> > > > +}
> > > This breaks the build of custom initrds on next
> > > 3f55e8574865de46bb795b60c3c3569567494aa7.
> > Can you try master branch, or an earlier next at
> > 49d4f8d81264b50e5d9c43a9d235c2a729164d28?
>
> The error also occurs on 49d4f8d8. See
> https://gitlab.com/cip-project/cip-core/isar-cip-core/-/jobs/12155333533.
This looks like a race condition. Rebuilding or building with sstate-
cache does not run into this issue.
Looking into it.
Felix
>
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
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/245b4cc8328aaccca63ab7a52be6926ffa8614d5.camel%40siemens.com.
next prev parent reply other threads:[~2025-11-24 9:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 13:24 [PATCH v4 00/10] Add " 'Felix Moessbauer' via isar-users
2025-11-17 13:24 ` [PATCH v4 01/10] refactor: move get_rootfs_distro from sdk into rootfs 'Felix Moessbauer' via isar-users
2025-11-17 13:24 ` [PATCH v4 02/10] meta: package python libraries for SBOM generation 'Felix Moessbauer' via isar-users
2025-11-17 13:24 ` [PATCH v4 03/10] meta: package python3-debsbom 'Felix Moessbauer' via isar-users
2025-11-17 13:24 ` [PATCH v4 04/10] meta: add SBOM generation with debsbom 'Felix Moessbauer' via isar-users
2025-11-19 15:54 ` 'Quirin Gylstorff' via isar-users
2025-11-19 16:58 ` Zhihang Wei
2025-11-20 11:07 ` 'Quirin Gylstorff' via isar-users
2025-11-24 9:16 ` 'MOESSBAUER, Felix' via isar-users [this message]
2025-11-17 13:24 ` [PATCH v4 05/10] override distro vendor in SBOM on Ubuntu 'Felix Moessbauer' via isar-users
2025-11-17 13:24 ` [PATCH v4 06/10] add support to add imager dependencies to BOM 'Felix Moessbauer' via isar-users
2025-11-17 13:24 ` [PATCH v4 07/10] wic: create uniform manifest describing all image components 'Felix Moessbauer' via isar-users
2025-11-17 13:24 ` [PATCH v4 08/10] qemuamd64: add IMAGER_BOM entries 'Felix Moessbauer' via isar-users
2025-11-17 13:24 ` [PATCH v4 09/10] imager: create SBOM of IMAGER_BOM packages 'Felix Moessbauer' via isar-users
2025-11-17 13:24 ` [PATCH v4 10/10] wic: create uniform SBOM describing all image components 'Felix Moessbauer' 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=245b4cc8328aaccca63ab7a52be6926ffa8614d5.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=quirin.gylstorff@siemens.com \
--cc=wzh@ilbers.de \
/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