From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 0/15] Add preliminary support for Linux containers
Date: Wed, 08 Jul 2015 14:46:26 +0200 [thread overview]
Message-ID: <87oajmlsv1.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=Rwfavb_eHOXDeBpHQKeGJPQQfT_+PMHK+wosGvKpgQCn12g@mail.gmail.com> (David Thompson's message of "Tue, 7 Jul 2015 18:35:53 -0400")
"Thompson, David" <dthompson2@worcester.edu> skribis:
> On Tue, Jul 7, 2015 at 6:28 AM, Ludovic Courtès <ludo@gnu.org> wrote:
[...]
>>> (lambda ()
>>> (sethostname "guix-0.8.3"))
>>
>> Surprisingly, calling ‘getpid’ in the thunk returns the PID of the
>> parent (I was expecting it to return 1.) Not sure why that is the
>> case. I’m still amazed that this works as non-root, BTW.
>
> The first process created inside the PID namespace gets the honor of
> being PID 1, not the process created with the 'clone' call.
>
> For more information, see: https://lwn.net/Articles/532748/
To me, the thunk above is just like ‘childFunc’ in
<https://lwn.net/Articles/533492/>–i.e., it’s the procedure that ‘clone’
calls in the first child process of the new PID name space.
What am I missing?
>> There’s an issue when the parent’s Guile is not mapped into the
>> container’s file system: ‘use-modules’ forms and auto-loading will fail.
>> For instance, I did (use-modules (ice-9 ftw)) in the parent and called
>> ‘scandir’ in the child, but that failed because of an attempt to
>> auto-load (ice-9 i18n), which is unavailable in the container.
>
> Hmm, I don't know of a way to deal with that other than the user being
> careful to bind-mount in the Guile modules they need.
Right. Maybe the best we can do is to add a word of caution in the
docstring or something.
> Hmm, there's various reasons that EINVAL would be thrown. Could you
> readlink "those" files, that is /proc/<pid-outside-container>/ns/user
> and /proc/<pid-inside-container>/ns/user, and tell me if the contents
> are the same? They shouldn't be, but this will eliminate one of the
> possible causes of EINVAL.
It turns out I was targeting the wrong PID.
>> Also, I think we should add --expose and --share as for ‘guix system’,
>> though that can come later.
>
> Yes, I also really want that, but it's a task for another time.
Sure.
>>> Here's how you build it:
>>>
>>> guix system container container.scm
>>
>> Very neat. I wonder if that should automatically override the
>> ‘file-systems’ field to be ‘%container-file-systems’, so that one can
>> reuse existing OS declarations unmodified. WDYT?
>
> This would be a better user experience, for sure. I thought about
> this, but I don't know how to do it in a way that isn't surprising or
> just broken. Ideas?
IMO it’d be fine to simply override the subset of ‘file-systems’ that
clashes with ‘%container-file-systems’, similar to what
‘virtualized-operating-system’ does in (gnu system vm).
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-07-08 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 13:01 [PATCH 0/15] Add preliminary support for Linux containers David Thompson
2015-07-07 10:28 ` Ludovic Courtès
2015-07-07 22:35 ` Thompson, David
2015-07-08 12:46 ` Ludovic Courtès [this message]
2015-07-08 13:00 ` Thompson, David
2015-07-08 21:59 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oajmlsv1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).