Re: question about builder and the container

["Roberto A. Foglietta" <roberto.foglietta@gmail.com>]

On Wed, 4 Jan 2023 at 13:31, Henning Schild <henning.schild@siemens.com> wrote:
>
> Am Wed, 4 Jan 2023 11:19:17 +0100
> schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
>
> > 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.
>
> builder is something coming from your kas container, i guess if you did
> native isar it would be your user on your machine
>

The problem obviously is not the builder user as default user but the
fact that rootfs belong to nobody:nogroup and thus sudo/su fail to
give the administrative privileges because of security reasons about
ownership. This is quite strange / uncommon and should have a specific
reason, suppose.

Best regards, R-