Linux Container Development
 help / color / mirror / Atom feed
From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Martin Fick <mogulguy-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: NFS Kernel server inside a container
Date: Sat, 29 May 2010 15:11:36 -0700	[thread overview]
Message-ID: <m1y6f2gxyf.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <187493.1732.qm-4AwnY8zbAf+vuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org> (Martin Fick's message of "Tue\, 18 May 2010 14\:09\:26 -0700 \(PDT\)")

Martin Fick <mogulguy-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> writes:

> --- On Tue, 5/18/10, Michael Tokarev <mjt-XAri/EZa3C4vJsYlp49lxw@public.gmane.org> wrote:
>> 18.05.2010 22:51, Martin Fick wrote:
>> >    FATAL: Could not load
>> /lib/modules/2.6.32-trunk-vserver-686/modules.dep: No such
>> file or directory
>> 
>> Obviously you have to have necessary modules in the
>> container in order to _load_ them.  But it is simpler
>> to pre-load all required modules from the host system
>> instead.
>
> Right, I actually ran the kernel server on the host 
> too, just to make sure the modules were loaded.
>
>> Actually it does not work even after solving
>> module issue.  I asked about this very issue
>> at the end of last year (I think), but no one
>> answered.  It looks like knfsd threads are
>> working in "global" (i.e host) namespace, not
>> in the container namespace, or the said
>> namespace isn't being set up correctly in
>> the kernel.  In any way, nfs service needs
>> to be "containerized" properly before being
>> useful inside a container, which is not done
>> currently, it seems.
>
> Is anyone working on this?  It certainly
> would be a very useful feature. :)  If it
> is only a matter of setting up the 
> container appropriately, any ideas how to
> do that? Thanks,

I remember doing some work a while ago and to ensure it fails
properly.  Getting knfsd updated to work in a network namespace should
be possible, but there are a lot of interactions, and isn't immediately
clear how the struct net would be passed to the functions that need it.

In short it looked doable, but I don't have any immediate plans to make it
happen but I would like to see it happen.

Eric

  parent reply	other threads:[~2010-05-29 22:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 21:09 NFS Kernel server inside a container Martin Fick
     [not found] ` <187493.1732.qm-4AwnY8zbAf+vuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-05-29 22:11   ` Eric W. Biederman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-05-18 18:51 Martin Fick
     [not found] ` <259227.79616.qm-UkVgyPgTERivuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-05-18 19:46   ` Michael Tokarev
2010-05-19  9:59   ` Daniel Lezcano
     [not found]     ` <4BF3B677.7080601-GANU6spQydw@public.gmane.org>
2010-05-19 15:26       ` Martin Fick
     [not found]         ` <516306.35958.qm-xC2hcER8YRCvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-05-19 15:45           ` Serge E. Hallyn
2010-05-19 19:33           ` Daniel Lezcano

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=m1y6f2gxyf.fsf@fess.ebiederm.org \
    --to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=mogulguy-/E1597aS9LQAvxtiuMwx3w@public.gmane.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox