From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Gylstorff, Quirin" <quirin.gylstorff@siemens.com>
Subject: Re: [PATCH v4 00/17] add support to build isar unprivileged
Date: Mon, 8 Jun 2026 09:31:33 +0000 [thread overview]
Message-ID: <364e5b31aade11ec20d1a65da29b6d6684662e42.camel@siemens.com> (raw)
In-Reply-To: <a320b6b7-39f5-4a75-8fe1-8851c162e3d3@ilbers.de>
On Thu, 2026-06-04 at 09:41 +0300, Anton Mikanovich wrote:
> 01.06.2026 14:34, 'Felix Moessbauer' via isar-users wrote:
> > Dear isar-users,
> >
> > currently isar requires password-less 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).
> >
> > Note, that this series can be tested on a custom kas-container build
> > provided in [1]. Hints how to migrate downstream layers are provided
> > in the API changelog.
> Hello Felix,
>
> This patchset version just have passed both fast and full CI.
Thanks for testing this. I propose to merge it soon (ish) to ensure all
future patches already use the run_privileged wrappers. This also
allows downstream layers (like isar-cip-core) to adjust to the wrappers
and offer more broad testing.
The corresponding kas patches also landed in kas:next.
CC Quirin
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/364e5b31aade11ec20d1a65da29b6d6684662e42.camel%40siemens.com.
next prev parent reply other threads:[~2026-06-08 9:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 11:34 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 01/17] refactor bootstrap: store rootfs tar with user permissions 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 02/17] deb-dl-dir: export without root privileges 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 03/17] download debs without locking 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 04/17] introduce wrappers for privileged execution 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 05/17] bootstrap: move cleanup trap to function 'Felix Moessbauer' via isar-users
2026-06-09 8:58 ` Anton Mikanovich
2026-06-09 11:02 ` 'MOESSBAUER, Felix' via isar-users
2026-06-01 11:34 ` [PATCH v4 06/17] rootfs: rework sstate caching of rootfs artifact 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 07/17] rootfs_generate_initramfs: rework deployment to avoid chowning 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 08/17] use bitbake function to generate mounting scripts 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 09/17] apt-fetcher: prepare for chroot specific fetching 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 10/17] add support for fully rootless builds 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 11/17] add helper script to clean artifacts in build dir 'Felix Moessbauer' via isar-users
2026-06-01 11:34 ` [PATCH v4 12/17] apt-fetcher: implement support for unshare backend 'Felix Moessbauer' via isar-users
2026-06-01 11:35 ` [PATCH v4 13/17] dpkg-source: implement multiarch " 'Felix Moessbauer' via isar-users
2026-06-01 11:35 ` [PATCH v4 14/17] use copy of sbom-chroot for sbom creation 'Felix Moessbauer' via isar-users
2026-06-01 11:35 ` [PATCH v4 15/17] add support for devshell on unshare backend 'Felix Moessbauer' via isar-users
2026-06-01 11:35 ` [PATCH v4 16/17] testsuite: add parameter to run tests in rootless mode 'Felix Moessbauer' via isar-users
2026-06-01 11:35 ` [PATCH v4 17/17] run-tests: add support for isar-rootless mode 'Felix Moessbauer' via isar-users
2026-06-04 6:41 ` [PATCH v4 00/17] add support to build isar unprivileged Anton Mikanovich
2026-06-08 9:31 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-06-09 9:02 ` Anton Mikanovich
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=364e5b31aade11ec20d1a65da29b6d6684662e42.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@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