public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: question about builder and the container
Date: Wed, 4 Jan 2023 11:19:17 +0100	[thread overview]
Message-ID: <CAJGKYO6fYwzjgNzV0TFWXuF=uzDquJ1aoAduTMZYAk6EC3pE5A@mail.gmail.com> (raw)
In-Reply-To: <20230103202151.206ac632@md1za8fc.ad001.siemens.net>

On Tue, 3 Jan 2023 at 20:21, Henning Schild <henning.schild@siemens.com> wrote:
>
> Am Tue, 3 Jan 2023 17:26:29 +0100
> schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
>
> > Hi all,
> >
> > I have noticed the following and the mount are the same, could someone
> > explain this to me?
> >
> > do_generate_keyrings() {
> >     sudo works, rootfs belong to root, whoami = builder
> > }
> > addtask generate_keyrings before do_build after do_unpack
> >
> > do_sudo_test() {
> >    sudo does NOT work, roofs belongs to nobody, whoami = builder
> > }
> > addtask sudo_test before do_build after generate_keyrings
>
> You are using an isar fork with bb2 already in and did not mark the task
> as network?
>

Thanks, I will give this a try to this:

do_start_imager_session[network] = "${TASK_USE_SUDO}"

but still I do not see why BB is using builder instead of root.

Best Regards, R-

  reply	other threads:[~2023-01-04 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 16:26 Roberto A. Foglietta
2023-01-03 19:21 ` Henning Schild
2023-01-04 10:19   ` Roberto A. Foglietta [this message]
2023-01-04 12:31     ` Henning Schild
2023-01-05 17:38       ` Roberto A. Foglietta

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='CAJGKYO6fYwzjgNzV0TFWXuF=uzDquJ1aoAduTMZYAk6EC3pE5A@mail.gmail.com' \
    --to=roberto.foglietta@gmail.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.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