From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "ubely@ilbers.de" <ubely@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"Hombourger, Cedric" <cedric.hombourger@siemens.com>
Cc: "Gylstorff, Quirin" <quirin.gylstorff@siemens.com>
Subject: Re: [PATCH v2 00/16] add support to build isar unprivileged
Date: Wed, 18 Mar 2026 08:04:28 +0000 [thread overview]
Message-ID: <7bce6b810199e96e8c68439b3e5d9121ad9f36ec.camel@siemens.com> (raw)
In-Reply-To: <e2fa098c-ea23-4b0f-9478-a1548e2695fc@siemens.com>
On Wed, 2026-03-18 at 07:02 +0100, Jan Kiszka wrote:
> On 17.03.26 19:41, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
> > On Fri, 2026-02-27 at 15:57 +0100, 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).
> > >
> > > 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.
> > >
> >
> > Dear isar-users,
> >
> > I'm currently waiting for the isar release and then plan to send out a
> > v3 that adds support for the cached-base-repo and src / dbg package
> > downloading. By that, the series should be feature complete.
> >
> > The last remaining aspect I don't have a solution to (yet) is the
> > sbuild_dpkg_log_export in dpkg.bbclass. To me it looks like the dpkg
> > dump is generated but never consumed anywhere. If someone could guide
> > me how this is processed, I'll implement support for this as well.
> >
>
> You read 03c0c7154d1632b92c9420ceb23706cc959b7cb3? Adding Uladzimir.
Yes, of course. But as I said, the file is not consumed anywhere.
A deeper investigation shows that this originally happened in deb-dl-
dir "is_not_part_of_current_build", but was removed in
f0da749f265e38d803da6566d680649d18f10c1f ("deb-dl-dir: remove excessive
calls to dpkg-deb in debsrc_download") by Cedric (now added as well).
Either the new implementation in f0da749f does not need the
dpkg_common.log file anymore (but forgot to remove the creation logic),
or the fix from 03c0c7154d is not working anymore.
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/7bce6b810199e96e8c68439b3e5d9121ad9f36ec.camel%40siemens.com.
prev parent reply other threads:[~2026-03-18 8:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 14:57 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 01/16] refactor bootstrap: store rootfs tar with user permissions 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 02/16] deb-dl-dir: export without root privileges 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 03/16] download debs without locking 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 04/16] introduce wrappers for privileged execution 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 05/16] bootstrap: move cleanup trap to function 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 06/16] rootfs: rework sstate caching of rootfs artifact 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 07/16] rootfs_generate_initramfs: rework deployment to avoid chowning 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 08/16] use bitbake function to generate mounting scripts 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 09/16] apt-fetcher: prepare for chroot specific fetching 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 10/16] add support for fully rootless builds 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 11/16] add helper script to clean artifacts in build dir 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 12/16] apt-fetcher: implement support for unshare backend 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 13/16] dpkg-source: implement multiarch " 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 14/16] use copy of sbom-chroot for sbom creation 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 15/16] add support for devshell on unshare backend 'Felix Moessbauer' via isar-users
2026-02-27 14:57 ` [PATCH v2 16/16] compat: handle user errors gracefully to avoid parser splat 'Felix Moessbauer' via isar-users
2026-03-17 18:41 ` [PATCH v2 00/16] add support to build isar unprivileged 'MOESSBAUER, Felix' via isar-users
2026-03-18 6:02 ` 'Jan Kiszka' via isar-users
2026-03-18 8:04 ` 'MOESSBAUER, Felix' via isar-users [this message]
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=7bce6b810199e96e8c68439b3e5d9121ad9f36ec.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=cedric.hombourger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.com \
--cc=ubely@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