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>,
"wzh@ilbers.de" <wzh@ilbers.de>
Subject: Re: [PATCH v6 00/17] add support to build isar unprivileged
Date: Thu, 25 Jun 2026 08:59:56 +0000 [thread overview]
Message-ID: <8b64ce39d3096fd3399056ae2aabf36d763ba88c.camel@siemens.com> (raw)
In-Reply-To: <20260615092458.259691-1-felix.moessbauer@siemens.com>
On Mon, 2026-06-15 at 11:24 +0200, Felix Moessbauer 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).
Hi,
are there any news on this? As this series has been successfully tested
in privileged mode, I would like to get it merged, so subsequent
patches already can use the run_privileged helpers.
Cleanups and improvements still can be done later on, but my fear is
that we will get a lot of back-and-forth between sudo and
run_privileged if not merged.
I also have some patches regarding the rootfs_postprocess idempotency
issues in my pipeline which also depend on the run_privileged wrappers.
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/8b64ce39d3096fd3399056ae2aabf36d763ba88c.camel%40siemens.com.
next prev parent reply other threads:[~2026-06-25 9:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 9:24 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 01/17] refactor bootstrap: store rootfs tar with user permissions 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 02/17] deb-dl-dir: export without root privileges 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 03/17] download debs without locking 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 04/17] introduce wrappers for privileged execution 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 05/17] bootstrap: move cleanup trap to function 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 06/17] rootfs: rework sstate caching of rootfs artifact 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 07/17] rootfs_generate_initramfs: rework deployment to avoid chowning 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 08/17] use bitbake function to generate mounting scripts 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 09/17] apt-fetcher: prepare for chroot specific fetching 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 10/17] add support for fully rootless builds 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 11/17] add helper script to clean artifacts in build dir 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 12/17] apt-fetcher: implement support for unshare backend 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 13/17] dpkg-source: implement multiarch " 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 14/17] use copy of sbom-chroot for sbom creation 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 15/17] add support for devshell on unshare backend 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 16/17] testsuite: add parameter to run tests in rootless mode 'Felix Moessbauer' via isar-users
2026-06-15 9:24 ` [PATCH v6 17/17] run-tests: add support for isar-rootless mode 'Felix Moessbauer' via isar-users
2026-06-19 9:08 ` Zhihang Wei
2026-06-19 10:03 ` 'MOESSBAUER, Felix' via isar-users
2026-06-19 14:32 ` Zhihang Wei
2026-06-22 16:25 ` 'MOESSBAUER, Felix' via isar-users
2026-06-22 18:55 ` 'Jan Kiszka' via isar-users
2026-06-22 19:53 ` 'Jan Kiszka' via isar-users
2026-06-22 20:23 ` 'MOESSBAUER, Felix' via isar-users
2026-06-22 20:53 ` 'Jan Kiszka' via isar-users
2026-06-23 15:17 ` Zhihang Wei
2026-06-23 22:13 ` 'Jan Kiszka' via isar-users
2026-06-19 9:00 ` [PATCH v6 00/17] add support to build isar unprivileged Zhihang Wei
2026-06-19 10:13 ` 'MOESSBAUER, Felix' via isar-users
2026-06-22 8:06 ` Zhihang Wei
2026-06-25 8:59 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-06-25 12:58 ` Zhihang Wei
2026-06-25 13:27 ` 'MOESSBAUER, Felix' via isar-users
2026-06-25 14:39 ` Zhihang Wei
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=8b64ce39d3096fd3399056ae2aabf36d763ba88c.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@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