From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: Re: [PATCH] kas: Support kas build system selection
Date: Tue, 9 Jun 2026 16:08:13 +0200 [thread overview]
Message-ID: <40aee07a-beb6-4c8f-b70e-f10900bccd02@siemens.com> (raw)
In-Reply-To: <20260609085346.3949936-1-amikan@ilbers.de>
On 09.06.26 10:53, Anton Mikanovich wrote:
> This adds yaml Kconfig options that allow to choose kas build system
> from the following list:
>
> --isar-rootless
> --isar-privileged
>
> After moving to rootless kas container previously used "--isar" option
> turns deprecated and should be replaced by "--isar-privileged".
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> Kconfig | 3 ++-
> kas/opt/Kconfig | 20 ++++++++++++++++++++
> 2 files changed, 22 insertions(+), 1 deletion(-)
>
> diff --git a/Kconfig b/Kconfig
> index 66dd4112..cfea1902 100644
> --- a/Kconfig
> +++ b/Kconfig
> @@ -1,5 +1,5 @@
> # This software is a part of Isar.
> -# Copyright (C) 2023 ilbers GmbH
> +# Copyright (C) 2023-2026 ilbers GmbH
> #
> # SPDX-License-Identifier: MIT
> #
> @@ -14,6 +14,7 @@ config KAS_INCLUDE_MAIN
>
> config KAS_BUILD_SYSTEM
> string
> + default "isar-privileged" if KAS_BUILD_SYSTEM_ISAR_PRIVILEGED
> default "isar-rootless"
>
> source "kas/machine/Kconfig"
> diff --git a/kas/opt/Kconfig b/kas/opt/Kconfig
> index ac9b2f55..1bea49b8 100644
> --- a/kas/opt/Kconfig
> +++ b/kas/opt/Kconfig
> @@ -115,6 +115,26 @@ config KAS_INCLUDE_USER_ISAR
>
> endmenu
>
> +
> +menu "Kas build system"
> +
> +choice
> + prompt "Kas build system"
> + default KAS_BUILD_SYSTEM_ISAR_ROOTLESS
> + help
> + Rootless build mode is using unshare syscall to avoid security issues.
> + Otherwize privileged mode with sudo permissions still can be used.
> +
> +config KAS_BUILD_SYSTEM_ISAR_ROOTLESS
> + bool "Rootless (--isar-rootless)"
> +
> +config KAS_BUILD_SYSTEM_ISAR_PRIVILEGED
> + bool "Privileged (--isar-privileged)"
> +
> +endchoice
> +
> +endmenu
> +
> config KAS_IMAGE_FSTYPES
> string "Additional image fstypes"
> default ""
As Felix already pointed out, this will not work. I would recommend to
stick with privileged builds until there is at least a kas release which
comes with the required support. Then, Isar could switch its default
over to rootless, leaving privileged mode only via command line
selection for CI purposes.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
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/40aee07a-beb6-4c8f-b70e-f10900bccd02%40siemens.com.
prev parent reply other threads:[~2026-06-09 14:08 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
2026-06-09 11:30 ` 'MOESSBAUER, Felix' via isar-users
2026-06-09 14:08 ` 'Jan Kiszka' 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=40aee07a-beb6-4c8f-b70e-f10900bccd02@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@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