OpenVZ Forum


Home » Mailing lists » Users » rpc.idmapd in container
Re: rpc.idmapd in container [message #46110 is a reply to message #46026] Thu, 26 April 2012 15:53 Go to previous messageGo to previous message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

On 04/23/2012 12:34 PM, Björn Lindgren wrote:
> Hi,
>
> I'm trying to setup NFS4 in a container but are having trouble getting
> the rpc.idmapd daemon process to work.
>
> At startup rpc.idmapd tries to access two proc files which are missing
> in the container.
>
> /proc/net/rpc/nfs4.nametoid/channel
> /proc/net/rpc/nfs4.idtoname/channel
>
> They are available on the host node through kernel module nfsd.ko
>
> How do I configure OpenVZ to get these?
>
> Running CentOS 6.2 with
> 042stab053.5< http://wiki.openvz.org/News/updates#Kernel_RHEL6_042stab053. 5_released>

NFS server (and client) inside container is fully supported, for it to
work you need to
(1) have kernel module nfsd loaded before starting CT
(2) have feature nfsd turned on for CT

Both of this is described at
http://wiki.openvz.org/NFS_server_inside_container

Having said that, only NFS v2 and NFS v3 are supported inside CT.

We are currently working on making NFS v4 work inside containers, but we
do it for mainline
kernels rather than in RHEL6 kernel. So whenever we will port OpenVZ to
any of 3.3 kernels,
it will most probably have NFS v4 support. RHEL7-based OpenVZ kernel
will have it, too.

Is there any specific reason why you need NFS v4 and not v3?


Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: HN using swap instead of ram
Next Topic: High Swap Load
Goto Forum:
  


Current Time: Thu Jul 17 21:02:36 GMT 2025

Total time taken to generate the page: 0.05388 seconds