Search results

No, it uses the default apparmor profile for any lxc container. I don't remember seeing this line in my config file before. To be clear, my container is privileged, I couldn't setup an nfs server in an unprivileged container. Are any other service working in your container? If yes, this is a...

Here you go : arch: amd64 cores: 1 features: fuse=1,mount=nfs;cifs;nfs;cifs,nesting=1 hostname: myvm0 memory: 512 mp0: /srv/vm/storage,mp=/media net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=xx:xx:xx:xx:xx:xx,ip=dhcp,ip6=dhcp,type=veth onboot: 1 ostype: ubuntu rootfs...

I found the issue ! I was misled by dmesg, apparmor wasn't the cause of the problem, rather, it came from the lxc template I was using. The 'debian-10.0-standard_10.0-1_amd64.tar.gz' just doesn't work past a reboot of the container. I'm running a container from the...

Just realized there may have been an error with the following line in /etc/pve/lxc/myid.conf : features: fuse=1,mount=nfs;nfs;cifs;nfs;cifs;nfs;cifs,nesting=1 which I changed to : features: fuse=1,mount=nfs;cifs,nesting=1 However, nothing's changed.

Hi, My host is Proxmox 6.1-8 and I've setup a privileged LXC (debian 10) container in which I want to run an NFS sever. The container's features are : features: fuse=1,mount=nfs;nfs;cifs;nfs;cifs;nfs;cifs,nesting=1 On first launch I installed nfs-kernel-server and it could run however, once I...