2,253
edits
Changes
m
Robot: Automated text replacement (-VE +container)
use a user-space NFS server daemon or use an in-kernel implementation
of NFS server. Some peculiarities appear if you intend to run NFS server
in [[VEcontainer]].
{{Note|for information about NFS client inside VEcontainer, see [[NFS]].}}
== Kernel NFS server ==
to use NFS server on [[HN]].
In-kernel NFS server runs kernel threads to service requests of clients.
But for security reasons kernel threads are prohibited in [[VEcontainer]]s! So you won'tbe able to run NFS server inside [[VEcontainer]] without patching the kernel.
== User-space NFS server ==
The reason is that these daemons check the major number of the device where the directory to export resides.
If major equals 0 then daemons assume that it is NFS and don't want to re-export it. Symptoms are
that clients will always get a "permission denied" error. Simfs (the file system on which VE container is located)
is associated with so called unnamed device, in which major equals 0. So, to prevent daemons from checking for
re-exporting — just use this <code>-r</code> option.