From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Sukadev Bhattiprolu
<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
nfs-ganesha-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: nfs-ganesha with Linux containers
Date: Wed, 13 Feb 2013 11:14:40 -0800 [thread overview]
Message-ID: <87liasuiu7.fsf@xmission.com> (raw)
In-Reply-To: <20130213074747.GA19635-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> (Sukadev Bhattiprolu's message of "Tue, 12 Feb 2013 23:47:47 -0800")
Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> writes:
> I have nfs-ganesha [1.5.1] with FSAL_VFS running on Linux 3.7.0-rc8 on
> an x86_64 RHEL6.2 system (the "host"). I can export the filesystems and
> mount from another system.
>
> I am trying to use nfs-Ganesha from within a Linux container on the same
> system.
>
> My container setup:
>
> On the REHL6.2 host, I have a directory, /export/vm1-root.
>
> The root of my linux container is bind mounted to that directory
> So a file '/export/vm1-root/foobar' is known to the container as
> '/foobar' and other files/directories in '/export' are not visible
> from the container.
>
> [ie it is as if the processes inside the containers have run 'chroot'
> into /export/vm1-root and can't escape out of this].
Have you run pivot_root so you can throw away your old mounts? I don't
know a thing about the nfs ganesha user space daemon but /proc/mounts
should be the only way it could detect your mounts are in a container
and do something odd or confusing.
Eric
next prev parent reply other threads:[~2013-02-13 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 7:47 nfs-ganesha with Linux containers Sukadev Bhattiprolu
[not found] ` <20130213074747.GA19635-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2013-02-13 19:14 ` Eric W. Biederman [this message]
[not found] ` <87liasuiu7.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2013-02-13 19:50 ` Sukadev Bhattiprolu
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=87liasuiu7.fsf@xmission.com \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=nfs-ganesha-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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