public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Ben Brenson <benbrenson89@googlemail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Isar fork
Date: Wed, 18 Oct 2017 05:11:00 -0700 (PDT)	[thread overview]
Message-ID: <0eeda167-efa1-4eaf-ade5-8d43d09f2c8a@googlegroups.com> (raw)
In-Reply-To: <3ad4ed89-de76-9a07-c2f5-3abea0583f68@siemens.com>


[-- Attachment #1.1: Type: text/plain, Size: 1210 bytes --]

Hi Claudius,

I see that you are using schroot. How is your progress on 'sudo' removal? 
>
 
schroot itself, doesn't solve the 'sudo' problem, but it's very useful for 
running common tasks when setting up a chroot, like mounting filesystems, 
setting up binfmt etc.
So basically it extends the chroot command itself. 

I haven't heard of schroot before, but from what I gather it needs a 
> privileged service to run in the background. 
>
 
I've never heard about or noticed that schroot needs a  privileged service 
running in the background. Maybe I have to check this.
The main cause for introducing the schroot feature, was to have a already 
implemented framework, when setting up chroots (mostly related to setting 
up mounts).
Since a lot of chroot tasks running in parallel, if searched for a reliable 
chroot extension.

What are your experience with it? Could it be used for all parts that 
> currently require root privileges? Have you tried it inside a docker 
> container? 
>

That is what I think the docker container is for solving the 'sudo' problem.
Running schroot inside a docker container is now problems and behaves 
exactly the same, like running it without schroot.

 Regards,
Benedikt

[-- Attachment #1.2: Type: text/html, Size: 1810 bytes --]

  reply	other threads:[~2017-10-18 12:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18  9:23 Ben Brenson
2017-10-18 11:16 ` Jan Kiszka
2017-10-18 11:56   ` Ben Brenson
2017-10-18 12:09     ` Jan Kiszka
2017-10-18 11:56 ` Claudius Heine
2017-10-18 12:11   ` Ben Brenson [this message]
2017-10-18 12:52     ` Claudius Heine
2017-10-18 14:02       ` Ben Brenson
2017-10-18 14:19         ` Henning Schild
2017-10-18 14:22         ` Claudius Heine

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=0eeda167-efa1-4eaf-ade5-8d43d09f2c8a@googlegroups.com \
    --to=benbrenson89@googlemail.com \
    --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