From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"Gylstorff, Quirin" <quirin.gylstorff@siemens.com>
Subject: Re: [PATCH v7 10/17] add support for fully rootless builds
Date: Fri, 3 Jul 2026 14:53:25 +0000 [thread overview]
Message-ID: <99b3c876bd27c5f7b2c895e3eb7a4e42bf7940e5.camel@siemens.com> (raw)
In-Reply-To: <20260625153651.762936-11-felix.moessbauer@siemens.com>
On Thu, 2026-06-25 at 17:36 +0200, Felix Moessbauer wrote:
> Currently isar requires passwordless sudo and an environment
> where mounting file systems is possible. This has proven problematic
> for security reasons, both when running in a privileged container or
> locally.
>
> To solve this, we implement fully rootless builds that rely on the
> unshare syscall which allows us to avoid sudo and instead operate in
> temporary kernel namespaces as a user that is just privileged within
> that namespace. This comes with some challenges regarding the handling
> of mounts (they are cleared when leaving the namespace), as well as
> cross namespace deployments (the outer user might not be able to access
> the inner data). For that, we rework the handling of mounts and artifact
> passing to make it compatible with both chroot modes (schroot and
> unshare).
>
> We intentionally do not switch the build_system in isar.yaml resp. the
> KAS_BUILD_SYSTEM in the menu KConfig, as there is no kas release with
> support for the new modes as of today. We further don't want to break
> backward compatibility with older kas versions of the isar examples.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> RECIPE-API-CHANGELOG.md | 20 +++++
> doc/user_manual.md | 2 +
> meta/classes-global/base.bbclass | 86 ++++++++++++++++++-
> meta/classes-recipe/deb-dl-dir.bbclass | 7 +-
> meta/classes-recipe/dpkg-base.bbclass | 22 ++++-
> meta/classes-recipe/dpkg.bbclass | 17 ++--
> .../image-locales-extension.bbclass | 9 +-
> .../image-tools-extension.bbclass | 84 ++++++++++++++++++
> meta/classes-recipe/image.bbclass | 7 +-
> .../imagetypes_container.bbclass | 4 +-
> meta/classes-recipe/imagetypes_wic.bbclass | 6 +-
> meta/classes-recipe/rootfs.bbclass | 45 ++++++++--
> meta/classes-recipe/sbuild.bbclass | 24 +++++-
> meta/classes-recipe/sdk.bbclass | 10 ++-
> meta/conf/bitbake.conf | 7 +-
> .../isar-mmdebstrap/isar-mmdebstrap.inc | 18 ++--
> .../sbuild-chroot/sbuild-chroot.inc | 24 +++++-
> 17 files changed, 354 insertions(+), 38 deletions(-)
>
[snip]
>
> ROOTFS_INSTALL_COMMAND += "rootfs_install_resolvconf"
> @@ -368,8 +388,13 @@ rootfs_install_pkgs_install[weight] = "8000"
> rootfs_install_pkgs_install[progress] = "custom:rootfs_progress.PkgsInstallProgressHandler"
> rootfs_install_pkgs_install[network] = "${TASK_USE_SUDO}"
> rootfs_install_pkgs_install() {
> - run_in_chroot "${ROOTFSDIR}" \
> + run_privileged_heredoc <<'EOF'
> + set -e
> + ${@insert_isar_mounts(d, d.getVar('ROOTFSDIR'), d.getVar('ROOTFS_MOUNTS')) if d.getVar('ISAR_CHROOT_MODE') == 'unshare' else ''}
> + find ${ROOTFSDIR}/isar-apt
^
This is a debugging leftover. Will be removed on next iteration.
Are there any further findings I should fix before sending?
Best regards,
Felix
--
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/99b3c876bd27c5f7b2c895e3eb7a4e42bf7940e5.camel%40siemens.com.
next prev parent reply other threads:[~2026-07-03 14:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 15:36 [PATCH v7 00/17] add support to build isar unprivileged 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 01/17] refactor bootstrap: store rootfs tar with user permissions 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 02/17] deb-dl-dir: export without root privileges 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 03/17] download debs without locking 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 04/17] introduce wrappers for privileged execution 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 05/17] bootstrap: move cleanup trap to function 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 06/17] rootfs: rework sstate caching of rootfs artifact 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 07/17] rootfs_generate_initramfs: rework deployment to avoid chowning 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 08/17] use bitbake function to generate mounting scripts 'Felix Moessbauer' via isar-users
2026-07-03 14:40 ` 'MOESSBAUER, Felix' via isar-users
2026-06-25 15:36 ` [PATCH v7 09/17] apt-fetcher: prepare for chroot specific fetching 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 10/17] add support for fully rootless builds 'Felix Moessbauer' via isar-users
2026-07-03 14:53 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-06-25 15:36 ` [PATCH v7 11/17] add helper script to clean artifacts in build dir 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 12/17] apt-fetcher: implement support for unshare backend 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 13/17] dpkg-source: implement multiarch " 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 14/17] use copy of sbom-chroot for sbom creation 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 15/17] add support for devshell on unshare backend 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 16/17] testsuite: add parameter to run tests in rootless mode 'Felix Moessbauer' via isar-users
2026-06-25 15:36 ` [PATCH v7 17/17] run-tests: add support for isar-rootless mode '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=99b3c876bd27c5f7b2c895e3eb7a4e42bf7940e5.camel@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