From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: michael.adler@siemens.com, jan.kiszka@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v2 1/2] add script to check if the current environment supports rootless builds
Date: Fri, 21 Aug 2026 15:12:27 +0200 [thread overview]
Message-ID: <20260821131229.2235147-1-felix.moessbauer@siemens.com> (raw)
Running builds in rootless mode has a lot of non obvious pre conditions.
To help the user check if his system is configured correctly, we provide
a script that checks the needed features. If a feature is missing, it
issues an error regarding what likely is the root cause.
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
Changes since v1:
- ensure rootless is enabled before calling bitbake-getvar
- add -v option to print the RUN_PRIVILEGED_CMD variable
scripts/isar-check-rootless | 55 +++++++++++++++++++++++++++++++++++++
1 file changed, 55 insertions(+)
create mode 100755 scripts/isar-check-rootless
diff --git a/scripts/isar-check-rootless b/scripts/isar-check-rootless
new file mode 100755
index 00000000..b5197111
--- /dev/null
+++ b/scripts/isar-check-rootless
@@ -0,0 +1,55 @@
+#!/bin/sh
+# Copyright (C) 2026 Siemens AG
+# SPDX-License-Identifier: MIT
+#
+# Helper script to check if the current environment supports unprivileged
+# rootless builds with unshare.
+# Returns 0 if supported, otherwise returns 1 and prints an error message to stderr.
+
+verbose=0
+if [ "$1" = "-v" ]; then
+ verbose=1
+fi
+
+if ! run_privileged_cmd=$( \
+ BB_ENV_PASSTHROUGH_ADDITIONS="${BB_ENV_PASSTHROUGH_ADDITIONS} ISAR_ROOTLESS" \
+ ISAR_ROOTLESS=1 bitbake-getvar -q --value RUN_PRIVILEGED_CMD); then
+ echo "error: cannot determine RUN_PRIVILEGED_CMD from BitBake" >&2
+ exit 1
+fi
+
+[ "$verbose" = 0 ] || echo "RUN_PRIVILEGED_CMD: $run_privileged_cmd" >&2
+
+if ! ${run_privileged_cmd} /bin/sh <<'EOF'
+ failed=0
+
+ fail() {
+ echo "error: $1" >&2
+ echo " likely cause: $2" >&2
+ failed=1
+ }
+
+ mountpoint=$(mktemp -d)
+ if [ -n "$mountpoint" ]; then
+ if ! mount -t proc proc "$mountpoint"; then
+ fail "cannot mount procfs in the user namespace" \
+ "procfs is over-mounted by the container runtime, or the host security policy blocks procfs mounts"
+ else
+ umount "$mountpoint"
+ fi
+ rmdir "$mountpoint"
+ fi
+
+ if ! setpriv --reuid=nobody --regid=nogroup --clear-groups /usr/bin/true; then
+ fail "cannot execute as nobody:nogroup in the user namespace" \
+ "the subuid / subgid ID range is too small or incomplete"
+ fi
+
+ exit "$failed"
+EOF
+then
+ echo "error: unprivileged rootless builds are not supported; see the checks above" >&2
+ exit 1
+fi
+
+echo "unprivileged rootless builds are supported"
--
2.55.0
--
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/20260821131229.2235147-1-felix.moessbauer%40siemens.com.
next reply other threads:[~2026-08-21 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 13:12 'Felix Moessbauer' via isar-users [this message]
2026-08-21 13:12 ` [PATCH v2 2/2] user_manual: document rootless build mode 'Felix Moessbauer' via isar-users
2026-08-31 9:29 ` [PATCH v2 1/2] add script to check if the current environment supports rootless builds 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=20260821131229.2235147-1-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=michael.adler@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