Re: fakechroot

[Henning Schild <henning.schild@siemens.com>]

Am Mon, 16 Sep 2019 10:38:44 +0200
schrieb "[ext] Quirin Gylstorff" <quirin.gylstorff@siemens.com>:

> On 9/13/19 2:11 PM, Baurzhan Ismagulov wrote:
> > On Fri, Sep 13, 2019 at 12:57:45PM +0200, Quirin Gylstorff wrote:  
> >> fakechroot, fakeroot and pseudo are all using a similar mechanism
> >> by modifying the LD_PRELOAD_PATH with there own Libraries and
> >> abstracting the necessary systemcalls. pseudo uses a sqlite
> >> Database to get a persistent view on the topic.  
> 
> 
> > 
> > Thanks, the persistent view was my actual question. I think we
> > should be looking at pseudo, since the tools without persistency
> > aren't going to work for our use case. Or do you see a possibility
> > for fakechroot fakeroot? 
> 
> 
> If using fakeroot and fakechroot, debootstrap knows it is running in
> a fakeroot and adapts itself to this environment. From the previous
> test with pseudo it does not do that for pseudo[1].
> 
> I did not test of pseudo runs with --variant=fakeroot.
> 
> [1] 
> https://groups.google.com/forum/#!msg/isar-users/WV0N4X2ZZMo/4EQI3c1wBQAJ

Debootstrap is just one "problem", and i think we had that running
without a privileged container or "root".

A full build involves potentially setting binfmt and running wic, which
brings in a lot of tools (filesystems, partitions, bootloaders). OE
knows them as "wtools_sysroot" and builds them with dynamic linking
(for the LD_PRELOAD trick).
But we use the ones from our target distro in buildchroot, and guess
what, they are essential system tools that are statically linked. So no
LD-messing with them ...

Lowering the privileges for some steps (like debootstrap) might be a
good idea, but i still do not see how to do a full Isar build without
root.

Henning

> > With kind regards,
> > Baurzhan.
> >   
> 
> Kind regards
> Quirin
>