Re: PRoot: Drop sudo around buildchroot

[Alexander Smirnov <asmirnov@ilbers.de>]

On 10/25/2017 05:58 PM, 'Benedikt Niedermayr' via isar-users wrote:
> Am 25.10.2017 um 11:48 schrieb Alexander Smirnov:
>>
>>
>> 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.
>>
> May there be a problem when all files belonging to the build user and 
> not to root?

That's exactly the topic why I started proot with buildchroot and why 
I'm asking about various test results (did you try? :-)).

In the VM that I've built with proot patch I see the following:

root@isar:~# ls -l /usr/bin/ | grep hello
-rwxr-xr-x 1 root root   18068 Oct 24 18:52 hello
root@isar:~#

So the file from hello package (which is built using proot) has root 
ownership.


In theory the problems could occur during generation of target 
filesystem, will see. But anyway, Yocto will do this without sudo, so 
probably here also this could be done.

Alex