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>
Subject: Re: [PATCH] kas: Support kas build system selection
Date: Tue, 9 Jun 2026 11:26:09 +0000 [thread overview]
Message-ID: <d42a8ae255c3847f0bf0a276783ade94d80a3754.camel@siemens.com> (raw)
In-Reply-To: <76c90852-b0a0-4cd8-893a-b36a1300060c@ilbers.de>
On Tue, 2026-06-09 at 14:07 +0300, Anton Mikanovich wrote:
> 09.06.2026 14:01, MOESSBAUER, Felix wrote:
> > On Tue, 2026-06-09 at 11:53 +0300, Anton Mikanovich wrote:
> > > config KAS_BUILD_SYSTEM
> > > string
> > > + default "isar-privileged" if KAS_BUILD_SYSTEM_ISAR_PRIVILEGED
> > > default "isar-rootless"
> > Note, that this will only work on re-execution of kas, i.e. you need to
> > save the config and then run kas build. Running kas menu + build does
> > not work, as it is in the wrong container / execution mode.
> >
> > Felix
> In this case previously set "--isar" value will be used, which is still
> supported but results in warning by kas.
> Is it a big problem?
Well... --isar and --isar-privileged are the same. We should anyways
use --isar to still support older kas releases (in fact we don't even
have a kas release which supports --isar-privileged yet).
The bigger issue is that kas-container --isar-rootless only affects how
the container is started, but not how the build is started. The build
is started based on the build_system entry in the config.yaml file,
whereby rootless mode sets the ISAR_ROOTLESS=1 variable in the local
config.
kas-container also reads the build_system value from the KConfig or
.config.yml and starts the container accordingly. By that, we have to
treat the build system mode (rootless or privileged) as INPUT to kas
menu instead of a KConfig option of the menu.
My proposal is to just keep the build_system as "isar" in both the
KConfig and isar.yaml for now (at least until we have a kas version
that supports both). Later on, we can model the switching.
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/d42a8ae255c3847f0bf0a276783ade94d80a3754.camel%40siemens.com.
next prev parent reply other threads:[~2026-06-09 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 8:53 Anton Mikanovich
2026-06-09 8:55 ` Anton Mikanovich
2026-06-09 11:01 ` 'MOESSBAUER, Felix' via isar-users
2026-06-09 11:07 ` Anton Mikanovich
2026-06-09 11:26 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-06-09 11:30 ` 'MOESSBAUER, Felix' via isar-users
2026-06-09 14:08 ` 'Jan Kiszka' 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=d42a8ae255c3847f0bf0a276783ade94d80a3754.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@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