nfs error in lxc

[huky]

I have installed nfs-ganesha in lxc and it looks well:

# showmount -e localhost
Export list for localhost:
/opt/dxtfiles (everyone)

but i could not mount it

# /usr/sbin/mount.nfs -vvv -o vers=3 localhost:/opt/dxtfiles /mnt/test/
mount.nfs: timeout set for Tue Dec 22 05:39:57 2020
mount.nfs: trying text-based options 'vers=3,addr=::1'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying ::1 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying ::1 prog 100005 vers 3 prot UDP port 40868
mount.nfs: mount(2): Operation not permitted
mount.nfs: Operation not permitted

i tired config

features: keyctl=1,nesting=1,mount=nfs

it still the same problem.


then i tired config

unprivileged: 0

the error is now:

mount.nfs -v localhost:/opt/dxtfiles /mnt/test/
mount.nfs: not installed setuid - "user" NFS mounts not supported.

i just upgraded from v5.4

# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-26-pve: 4.15.18-54
pve-kernel-4.15.18-24-pve: 4.15.18-52
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.4.98-5-pve: 4.4.98-105
pve-kernel-4.4.95-1-pve: 4.4.95-99
pve-kernel-4.4.40-1-pve: 4.4.40-82
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.4.19-1-pve: 4.4.19-66
ceph: 12.2.13-pve1
ceph-fuse: 12.2.13-pve1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.0-1
proxmox-backup-client: 1.0.6-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-2
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

 

[Alwin]

It seems that running NFS-Ganesha in a container will need some relaxation of security.
https://discuss.linuxcontainers.org/t/nfs-ganesha-in-lxc/2401
https://github.com/nfs-ganesha/nfs-ganesha/issues/420

Best to create a fresh privileged container. Or restore a container from backup by removing the unprivileged flag.

 

[Rainerle]

You might want to vote this up:
https://forum.proxmox.com/threads/h...a-proxmox-cluster-with-ceph.80967/post-363314

 

[Lemure]

It seems that running NFS-Ganesha in a container will need some relaxation of security.
https://discuss.linuxcontainers.org/t/nfs-ganesha-in-lxc/2401
https://github.com/nfs-ganesha/nfs-ganesha/issues/420

Best to create a fresh privileged container. Or restore a container from backup by removing the unprivileged flag.

As a Proxmox newbie, can I ask what is the point of nfs-ganesha over nfs-kernel-server now that both require a privileged container to run?

 

[Rainerle]

nfs-ganesha runs in user space, so if it hangs or crashes in the CT (LXC) container it will not take the Proxmox Host down with it.

If the nfs-kernel-server in a CT container has problems it might hang the Proxmox host.

It is better to run a nfs-kernel-server within a Proxmox VM (KVM).

 

[Tony]

nfs-ganesha runs in user space, so if it hangs or crashes in the CT (LXC) container it will not take the Proxmox Host down with it.

If the nfs-kernel-server in a CT container has problems it might hang the Proxmox host.

It is better to run a nfs-kernel-server within a Proxmox VM (KVM).

can disk IO problem in a CT hang the Proxmox host? I experienced this problem with OpenVZ in the past, too.

I am trying to decide how to export NFS to some VMs: via host, CT or VM. A VM has best isolation, but the downside is that I must locate a disk to the VM. The route via CT is just opposite: I can bind-mount a directory from host and allocate as much space as needed, but it seems to have its downsides, too.