From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: PRoot: Drop sudo around buildchroot
Date: Thu, 2 Nov 2017 18:22:07 +0100 [thread overview]
Message-ID: <20171102182207.4af15dfe@md1em3qc> (raw)
In-Reply-To: <20171102181908.6108f3be@md1em3qc>
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".
> Now i waited for a long time, proot seems to slow things down a lot.
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.
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.
> >
>
next prev parent reply other threads:[~2017-11-02 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 19:34 Alexander Smirnov
2017-10-24 20:22 ` Jan Kiszka
2017-10-25 9:48 ` Alexander Smirnov
2017-10-25 14:58 ` Benedikt Niedermayr
2017-10-25 15:29 ` Alexander Smirnov
2017-10-26 8:57 ` Ben Brenson
2017-11-02 17:19 ` Henning Schild
2017-11-02 17:22 ` Henning Schild [this message]
2017-11-03 9:00 ` Alexander Smirnov
2017-11-03 9:05 ` Jan Kiszka
2017-11-02 17:33 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171102182207.4af15dfe@md1em3qc \
--to=henning.schild@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox