From: Henning Schild <henning.schild@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: PRoot experiments
Date: Thu, 19 Oct 2017 10:59:56 +0200 [thread overview]
Message-ID: <20171019105956.368e1297@md1em3qc> (raw)
In-Reply-To: <0b129e7e-f633-70d8-34fe-07cbb34fac13@ilbers.de>
On Wed, 18 Oct 2017 15:29:36 +0300
Alexander Smirnov <asmirnov@ilbers.de> wrote:
> Hi all,
>
> I've performed several experiments with PRoot:
>
> 1. Generate multistrap filesystem:
>
> As reference I've used the following resource:
> https://github.com/josch/polystrap/blob/master/polystrap.sh
>
> So, I was able to run the following command without root permissions:
>
> $ PROOT_NO_SECCOMP=1 proot -0 /usr/sbin/multistrap -f multistrap.conf
> -d test
>
> After this command execution I have 'test' folder which looks quite
> similar to one, generated with sudo (at least 'du -sm' is the same).
>
> 2. Run commands in PRoot chroot:
>
> I'm successfully able to run PRoot chroot for various architectures:
>
> $ PROOT_NO_SECCOMP=1 proot -0 -r ./test /bin/bash
>
> Also I was able to run: 'dpkg --configure -a' in these chroots.
>
> 3. Mount of various work folders:
>
> Mount forlder using PRoot seems also works good:
>
> $ PROOT_NO_SECCOMP=1 proot -0 -b /proc -b /dev -r ./test /bin/bash
>
> And in this chroot I have /proc and /dev mounted.
>
>
> So, my brief conclusion is: PRoot could be a good option for Isar. It
> seems that it's designed to support exact features that are required
> for Isar. :-)
Sounds promising. The last release of proot was in 2014 but when
looking at github it seems it is not dead yet.
Would be nice to get a solution to the sudo issue, otherwise we can
resort to VMs. But docker or "native" is more light-weight and easier
to integrate into CI.
Henning
> I'd like to try to implement simple PoC to test if *.deb package
> could be generated in Isar without 'sudo'.
>
> BTW: PRoot is a part of standard Debian, so it could be installed via
> 'apt-get', no custom repos required.
>
next prev parent reply other threads:[~2017-10-19 8:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 12:29 Alexander Smirnov
2017-10-19 8:59 ` Henning Schild [this message]
2017-10-19 10:10 ` Ben Brenson
[not found] ` <b0082bee-94d7-48c6-8582-93efc4171b59@googlegroups.com>
2017-10-19 10:14 ` Alexander Smirnov
2017-10-19 10:39 ` Claudius Heine
2017-10-19 10:44 ` Benedikt Niedermayr
2017-10-19 11:08 ` Claudius Heine
2017-10-19 11:15 ` Benedikt Niedermayr
2017-10-19 11:37 ` Alexander Smirnov
2017-10-19 11:36 ` Benedikt Niedermayr
2017-10-19 11:40 ` Alexander Smirnov
2017-10-19 13:37 ` Ben Brenson
2017-10-20 8:18 ` Ben Brenson
2017-10-20 8:52 ` Claudius Heine
2017-10-20 9:21 ` Ben Brenson
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=20171019105956.368e1297@md1em3qc \
--to=henning.schild@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.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