Re: nfs-ganesha with Linux containers

[Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>]

Eric W. Biederman [ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org] wrote:
| 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

I used virsh/libvirt to create the container and libvirtd does the pivot_root().

| 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.

I had an error in the /etc/ganesha/vfs.ganesha.exports.conf. I fixed
that and forced an entry for / in container's /etc/mtab. I am now able
to export from the container and mount from an external host.

Sorry for the noise.

Suka