Re: PRoot: Drop sudo around buildchroot

[Alexander Smirnov <asmirnov@ilbers.de>]

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.

Alex

> 
> Henning
> 
>> And then i ended up with a long list of packages where "Errors were
>> encountered while processing:". Might be connected to docker...
>>
>> Did anyone else give that a try?
>>
>> Henning
>>
>> Am Wed, 25 Oct 2017 12:48:37 +0300
>> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
>>
>>> On 10/24/2017 11:22 PM, Jan Kiszka wrote:
>>>> On 2017-10-24 21:34, Alexander Smirnov wrote:
>>>>> Hello all,
>>>>>
>>>>> I've successfully dropped 'sudo' around buildchroot operations:
>>>>>
>>>>>    - Create buildchroot
>>>>>    - Build dpkg-base package (hello)
>>>>>    - Build dpkg-raw package (example-raw)
>>>>>
>>>>> The patch is quite small, proot works out-of-the box. I've tested
>>>>> the following configurations:
>>>>>
>>>>>    - multiconfig:qemuarm-wheezy:isar-image-base
>>>>>    - multiconfig:qemuarm-jessie:isar-image-base
>>>>>    - multiconfig:qemuarm-stretch:isar-image-base
>>>>>    - multiconfig:qemui386-jessie:isar-image-base
>>>>>    - multiconfig:qemui386-stretch:isar-image-base
>>>>>    - multiconfig:qemuamd64-jessie:isar-image-base
>>>>>    - multiconfig:qemuamd64-stretch:isar-image-base
>>>>>
>>>>> So proot is really good tool :-)
>>>>>
>>>>> If you'd like to reproduce the test, please try my branch:
>>>>> asmirnov/devel
>>>>>
>>>>> NOTE: do not forget to install proot: apt-get install proot
>>>>>
>>>>> Build command:
>>>>> $ bitbake multiconfig:qemuarm-wheezy:isar-image-base
>>>>> multiconfig:qemuarm-jessie:isar-image-base
>>>>> multiconfig:qemuarm-stretch:isar-image-base
>>>>> multiconfig:qemui386-jessie:isar-image-base
>>>>> multiconfig:qemui386-stretch:isar-image-base
>>>>> multiconfig:qemuamd64-jessie:isar-image-base
>>>>> multiconfig:qemuamd64-stretch:isar-image-base
>>>>>     
>>>>
>>>> Great news! Hope this passes all tests and then makes it into
>>>> master soon!
>>>
>>> I've tested QEMU machines for images listed above, no difference
>>> observed in comparison with original 'sudo' approach. But anyway,
>>> it would be nice if somebody else will test this, especially in
>>> customer project environment.
>>>    
>>
> 

-- 
With best regards,
Alexander Smirnov

ilbers GmbH
Baierbrunner Str. 28c
D-81379 Munich
+49 (89) 122 67 24-0
http://ilbers.de/
Commercial register Munich, HRB 214197
General manager: Baurzhan Ismagulov