From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: Martin Fick <mogulguy-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: NFS Kernel server inside a container
Date: Wed, 19 May 2010 11:59:19 +0200 [thread overview]
Message-ID: <4BF3B677.7080601@free.fr> (raw)
In-Reply-To: <259227.79616.qm-UkVgyPgTERivuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
On 05/18/2010 08:51 PM, Martin Fick wrote:
> Hello,
>
> I was wondering if it is possible to run an NFS kernel server inside a linux container?
>
> I tried setting one up on a debian (vserver enabled) kernel, and it seems to start the portmap, rpc.statd, rpc.idmapd rpc.mountd daemons inside the container, but I cannot seem to mount the filesystem from a client. I do get the following error message on server startup:
>
> FATAL: Could not load /lib/modules/2.6.32-trunk-vserver-686/modules.dep: No such file or directory
>
>
> When trying to mount on the client, after blocking on the mount for a while, I get:
>
> mount.nfs: mount system call failed
>
It may be possible your network configuration is not correct regarding
the nfs server access. Can you ping the nfs server from the container ?
> Any thoughts? Has anyone else done this? Should this be possible in the first place? Thanks,
>
I thought NFS was isolated through the mount namespace.
I have a nfs server on 172.20.0.1 exporting "/home".
On my host (IP 172.20.0.166), I mounted /home via nfs
I created a debian system container with its own rootfs and network.
Started it. As expected, the nfs mount point is unmounted as it does not
belong to the rootfs, and then I remounted /home from my container (IP
172.20.0.42). This mount point is private to the container and not
accessible from the other containers.
This is what you want to do ? Or did I miss something ?
Thanks
-- Daniel
next prev parent reply other threads:[~2010-05-19 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 18:51 NFS Kernel server inside a container 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 [this message]
[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
-- strict thread matches above, loose matches on Subject: below --
2010-05-18 21:09 Martin Fick
[not found] ` <187493.1732.qm-4AwnY8zbAf+vuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-05-29 22:11 ` Eric W. Biederman
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=4BF3B677.7080601@free.fr \
--to=daniel.lezcano-ganu6spqydw@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