Search results

Just a note about the changes needed to my NFS container after upgrading to Proxmox 5: After the upgrade of Proxmox, the NFS server inside the container didn't run anymore. I needed to upgrade the container to Debian 9 and start kernel-nfs-server via systemctl, that solved the start problems...

It's a bit confusing when you mix the topics "file system mounts between containers and/or node" and "network access to a directory". For filesystem mounts, AFAIK it is *not* possible to mount a directory from one container to another. To do so, the directory has to be part of the node...

Or vice versa: the line "lxc.mount.entry: /tank/data srv/data none bind,create=dir,optional 0 0" does mount a directory from the node filesystem (/tank/data) into a directory of the container (/srv/data in the container filesystem). I gues a mount from container to container is not possible...

No, on the Proxmox host itself I didn't install anything NFS specific, the nfs-kernel-server is installed and running in the LXC container only: On the Proxmox-Node (stuff was already installed with proxmox): root@proxmox:~# dpkg -l | grep nfs ii libnfsidmap2:amd64 0.25-5...

Solved: by adding the option "lxc.aa_profile: unconfined" to the container configuration

My attempt to run a NFS server within a LXC Linux Container failed. I used the debian based TurnKey Linux fileserver template and tried to activate the NFS kernel server within its LXC (/etc/exports were already configured): # /etc/init.d/nfs-kernel-server start mount: nfsd is write-protected...