From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Krishnakar, Srikanth" <srikanth.krishnakar@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "kas-devel@googlegroups.com" <kas-devel@googlegroups.com>
Subject: Re: Isar-based projects using kas-container and podman-rootless
Date: Tue, 28 Feb 2023 07:15:26 +0100 [thread overview]
Message-ID: <513677c9-f06d-1a58-07e6-265864aac86a@siemens.com> (raw)
In-Reply-To: <TYAPR06MB230385626C40701C9CAD97EDFDAC9@TYAPR06MB2303.apcprd06.prod.outlook.com>
On 28.02.23 06:58, Krishnakar, Srikanth wrote:
> Hello,
>
> Can we build Isar-based projects using kas-container+podman but without
> any privilege escalations of any sorts on the host (container may do
> whatever it needs to as long as it is not running with --privileged) ?
>
Nope, already because of missing namespace support for binfmt_misc
(stalled once again after https://lkml.org/lkml/2021/12/16/407).
I'm no longer up-to-date regarding how sbuild / schroot improved the
picture of going unprivileged inside podman one day, but there might be
still other roadblocks left.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2023-02-28 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 5:58 Krishnakar, Srikanth
2023-02-28 6:15 ` Jan Kiszka [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=513677c9-f06d-1a58-07e6-265864aac86a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=kas-devel@googlegroups.com \
--cc=srikanth.krishnakar@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