Re: PRoot: Drop sudo around buildchroot

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2017-11-03 10:00, Alexander Smirnov wrote:
> Hi,
> 
> On 11/02/2017 08:22 PM, Henning Schild wrote:
>> Am Thu, 2 Nov 2017 18:19:08 +0100
>> schrieb "[ext] Henning Schild" <henning.schild@siemens.com>:
>>
>>> Hi,
>>>
>>> i just gave that a try and failed to generate an image.
>>>
>>> When using docker you will need "--cap-add=SYS_PTRACE".
> 
> Yes, proot uses PTRACE system call.
> 
>>> Now i waited for a long time, proot seems to slow things down a lot.
>>
> 
> The default isar-image-base base has the following results:
> 
> === sudo ===
> 
> $ source isar-init-build-env b-sudo
> $ time bitbake multiconfig:qemuarm-wheezy:isar-image-base
> 
> real    10m59.270s
> user    6m16.220s
> sys    0m54.772s
> 
> === PRoot ===
> 
> $ source isar-init-build-env b-proot
> $ time bitbake multiconfig:qemuarm-wheezy:isar-image-base
> 
> real    16m4.493s
> user    6m9.423s
> sys    3m17.692s
> 
> So, building of buildchroot, hello and example-raw adds extra 6 minutes
> on my host.
> 
>> I also needed to change multistrap to /usr/sbin/multistrap because the
>> PATH inside proot does not cover /usr/sbin ... in case anyone wants to
>> try.
> 
> proot uses your current user's environment, so export
> PATH=$PATH:/usr/sbin before running bitbake should resolve your issue.

Given that the goal is unprivileged execution, this is not the right
solution. The path needs to be fixed inside the recipe.

Jan