public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "Kiszka, Jan" <jan.kiszka@siemens.com>,
	"cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/4] rootfs: introduce wrapper to run commands against a rootfs
Date: Thu, 5 Jun 2025 12:20:25 +0000	[thread overview]
Message-ID: <c23de399099b651ad8d6fbb264cbf69564c640f4.camel@siemens.com> (raw)
In-Reply-To: <b38288e179d92bca6d70957fba9b441145dcb76b.camel@siemens.com>

On Thu, 2025-06-05 at 06:42 +0000, Hombourger, Cedric (FT FDS CES LX)
wrote:
> On Thu, 2025-05-22 at 14:32 +0000, Moessbauer, Felix (FT RPD CED OES-
> DE) wrote:
> > On Mon, 2025-05-19 at 13:57 +0200, Cedric Hombourger wrote:
> > > "sudo chroot" is used in several places to run commands inside
> > > rootfs
> > > directories constructed by Isar. There are cases where a command
> > > could
> > > be used without elevated privileges as long as special folders
> > > such
> > > as
> > > /isar-apt are mounted (they are often referenced as /isar-apt in
> > > configuration files found in the target rootfs). For such cases,
> > > bubblewrap may be used to create a non-privileged namespace
> > > (either
> > > in a bare/native environment or within a docker/podman container)
> > > where the command will be executed as if chroot had been used.
> > > The
> > > rootfs may also be the host root file-system: this should however
> > > be used with care to avoid host contamination problems (note:
> > > Isar
> > > already relies on a number of host tools).
> > 
> > Hi, this looks promising. I gave it a try on some of our internal
> > layers (arm64) in a custom kas container under podman.
> > 
> > I'm wondering if this could also be used to run the apt in
> > do_rootfs_install natively (maybe in combination with dpkg --root).
> > 
> > Tested-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> 
> Dear maintainers, can we move forward with these changes or are there
> any concerns that need to be addressed?

If we decide to integrate this (which I vote for!), we should also add
the bubblewrap package to the upcoming kas 4.8 release (putting Jan in
CC).

Felix

> 
> Thank you!
> 
> > 
> > Felix
> > 
> > > 
> > > Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com>
> > > ---
> > >  RECIPE-API-CHANGELOG.md     |  6 ++++
> > >  doc/user_manual.md          |  1 +
> > >  meta/classes/rootfs.bbclass | 66
> > > +++++++++++++++++++++++++++++++++++++
> > >  3 files changed, 73 insertions(+)
> > > 
> > > diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
> > > index a4cf1338..725737b2 100644
> > > --- a/RECIPE-API-CHANGELOG.md
> > > +++ b/RECIPE-API-CHANGELOG.md
> > > @@ -722,3 +722,9 @@ Optional fields of the isar-apt repo can be
> > > controlled by adding to the
> > >  
> > >  Changes in next
> > >  ---------------
> > > +
> > > +### Require bubblewrap to run non-privileged commands with bind-
> > > mounts
> > > +
> > > +Isar occasionally needs to run commands within root file-systems
> > > that it
> > > +builds and with several bind-mounts (e.g. /isar-apt). bubblewrap
> > > may
> > > be
> > > +used in Isar classes instead of `sudo chroot`.
> > > diff --git a/doc/user_manual.md b/doc/user_manual.md
> > > index 0dc317c3..3cf1a9aa 100644
> > > --- a/doc/user_manual.md
> > > +++ b/doc/user_manual.md
> > > @@ -75,6 +75,7 @@ Install the following packages:
> > >  ```
> > >  apt install \
> > >    binfmt-support \
> > > +  bubblewrap \
> > >    bzip2 \
> > >    mmdebstrap \
> > >    arch-test \
> > > diff --git a/meta/classes/rootfs.bbclass
> > > b/meta/classes/rootfs.bbclass
> > > index 5f877962..5b96b414 100644
> > > --- a/meta/classes/rootfs.bbclass
> > > +++ b/meta/classes/rootfs.bbclass
> > > @@ -34,6 +34,72 @@ export LANG = "C"
> > >  export LANGUAGE = "C"
> > >  export LC_ALL = "C"
> > >  
> > > +# Execute a command against a rootfs and with isar-apt bind-
> > > mounted.
> > > +# Additional mounts may be specified using --bind <source>
> > > <target>
> > > and a
> > > +# custom directory for the command to be executed with --chdir
> > > <dir>. The
> > > +# command is assumed to follow the special "--" argument. This
> > > would
> > > replace
> > > +# "sudo chroot" calls especially when a native command may be
> > > used
> > > instead of
> > > +# chroot'ed command and without elevated privileges (the command
> > > will likely
> > > +# take the rootfs as argument; e.g. apt-get -o
> > > Dir=${ROOTFSDIR}).
> > > If
> > > the
> > > +# optional rootfs argument is omitted, the host rootfs will be
> > > used
> > > (e.g. to
> > > +# run native commands): this should be used with care.
> > > +#
> > > +# Usage: rootfs_cmd [options] [rootfs] -- command
> > > +#
> > > +rootfs_cmd() {
> > > +    set -- "$@"
> > > +    bwrap_args="--bind ${REPO_ISAR_DIR}/${DISTRO} /isar-apt"
> > > +    rootfs=""
> > > +
> > > +    while [ "${#}" -gt "0" ] && [ "${1}" != "--" ]; do
> > > +        case "${1}" in
> > > +            --bind)
> > > +                if [ "${#}" -lt "3" ]; then
> > > +                    bbfatal "--bind requires two arguments"
> > > +                fi
> > > +                bwrap_args="${bwrap_args} --bind ${2} ${3}"
> > > +                shift 3
> > > +                ;;
> > > +            --chdir)
> > > +                if [ "${#}" -lt "2" ]; then
> > > +                    bbfatal "${1} requires an argument"
> > > +                fi
> > > +                bwrap_args="${bwrap_args} ${1} ${2}"
> > > +                shift 2
> > > +                ;;
> > > +            -*)
> > > +                bbfatal "${1} is not a supported option!"
> > > +                ;;
> > > +            *)
> > > +                if [ -z "${rootfs}" ]; then
> > > +                    rootfs="${1}"
> > > +                    shift
> > > +                else
> > > +                    bbfatal "unexpected argument '${1}'"
> > > +                fi
> > > +                ;;
> > > +        esac
> > > +    done
> > > +
> > > +    if [ -n "${rootfs}" ]; then
> > > +        bwrap_args="${bwrap_args} --bind ${rootfs} ${rootfs}"
> > > +    fi
> > > +
> > > +    if [ "${#}" -le "1" ] || [ "${1}" != "--" ]; then
> > > +        bbfatal "no command specified (missing --)"
> > > +    fi
> > > +    shift  # remove "--", command and its arguments follows
> > > +
> > > +    for ro_d in bin etc lib lib64 sys usr var; do
> > > +        [ -d ${rootfs}/${ro_d} ] || continue
> > > +        bwrap_args="${bwrap_args} --ro-bind ${rootfs}/${ro_d}
> > > /${ro_d}"
> > > +    done
> > > +
> > > +    bwrap --unshare-user --unshare-pid ${bwrap_args} \
> > > +        --dev-bind /dev /dev --proc /proc --tmpfs /tmp \
> > > +        -- "${@}"
> > > +}
> > > +
> > >  rootfs_do_mounts[weight] = "3"
> > >  rootfs_do_mounts() {
> > >      sudo -s <<'EOSUDO'
> > 
> 
> -- 
> Cedric Hombourger
> Siemens AG
> www.siemens.com

-- 
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/c23de399099b651ad8d6fbb264cbf69564c640f4.camel%40siemens.com.

  reply	other threads:[~2025-06-05 12:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 15:07 [RFC PATCH 0/2] optimize caching of source packages 'Cedric Hombourger' via isar-users
2025-05-15 15:07 ` [RFC PATCH 1/2] rootfs: introduce wrapper to run native commands against a rootfs 'Cedric Hombourger' via isar-users
2025-05-19 11:57   ` [PATCH 0/4] non-privileged commands in chroot 'Cedric Hombourger' via isar-users
2025-05-19 11:57     ` [PATCH 1/4] rootfs: introduce wrapper to run commands against a rootfs 'Cedric Hombourger' via isar-users
2025-05-22 14:32       ` 'MOESSBAUER, Felix' via isar-users
2025-06-05  6:42         ` 'cedric.hombourger@siemens.com' via isar-users
2025-06-05 12:20           ` 'MOESSBAUER, Felix' via isar-users [this message]
2025-06-05 12:43             ` Baurzhan Ismagulov
2025-06-06  6:05               ` 'cedric.hombourger@siemens.com' via isar-users
2025-06-05 13:57       ` 'Jan Kiszka' via isar-users
2025-06-06  6:02         ` 'cedric.hombourger@siemens.com' via isar-users
2025-06-06  6:11           ` 'Jan Kiszka' via isar-users
2025-05-19 11:57     ` [PATCH 2/4] deb-dl-dir: optimize caching of source packages using apt natively 'Cedric Hombourger' via isar-users
2025-05-19 11:57     ` [PATCH 3/4] image-postproc-extension: refactor systemd version checks 'Cedric Hombourger' via isar-users
2025-05-19 11:57     ` [PATCH 4/4] image-postproc-extension: extract systemd's version using rootfs_cmd 'Cedric Hombourger' via isar-users
2025-05-19 13:33     ` [PATCH 0/4] non-privileged commands in chroot Srinuvasan Arjunan
2025-06-18 13:50     ` [PATCH v2 " 'Cedric Hombourger' via isar-users
2025-06-18 13:50       ` [PATCH v2 1/4] rootfs: introduce wrapper to run commands against a rootfs 'Cedric Hombourger' via isar-users
2025-06-18 13:50       ` [PATCH v2 2/4] deb-dl-dir: optimize caching of source packages using apt natively 'Cedric Hombourger' via isar-users
2025-06-18 13:50       ` [PATCH v2 3/4] image-postproc-extension: refactor systemd version checks 'Cedric Hombourger' via isar-users
2025-06-18 13:50       ` [PATCH v2 4/4] image-postproc-extension: extract systemd's version using rootfs_cmd 'Cedric Hombourger' via isar-users
2025-06-20  9:16         ` 'Quirin Gylstorff' via isar-users
2025-05-15 15:07 ` [RFC PATCH 2/2] deb-dl-dir: optimize caching of source packages using apt natively 'Cedric Hombourger' 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=c23de399099b651ad8d6fbb264cbf69564c640f4.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=cedric.hombourger@siemens.com \
    --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