If you absolutely have to, I would suggest establishing the FUSE mount on the Proxmox host and then using a bindmountpoint (e.g. "mp0: /path/on/host,mp=/path/in/container") to make it available in the container. If you establish the FUSE mounts inside the container, you will run into problems (lxc-freeze is not compatible with FUSE which means no snapshots and no suspend backup, you need to change all sorts of containment settings which lessens security, ..).
Can you share a little more on how one achieves this please? I make a connection on the server using:
sshfs myuser@192.168.abc.def:/ /mnt/xxx-win01
(myuser is a valid user on the connected to server and the command succeeds)
The mountpoint is added like this:
mp0: /mnt/xxx-win01, mp=/mnt/server
This creates the mountpoint in the LXC machine, but the content cannot be listed.
:~$ ls -la /mnt/server
ls: cannot access /mnt/server: Permission denied
The mount is world readable though
Is there some trick that I'm missing here?
sshfs myuser@192.168.abc.def:/ /mnt/xxx-win01
(myuser is a valid user on the connected to server and the command succeeds)
The mountpoint is added like this:
mp0: /mnt/xxx-win01, mp=/mnt/server
This creates the mountpoint in the LXC machine, but the content cannot be listed.
:~$ ls -la /mnt/server
ls: cannot access /mnt/server: Permission denied
The mount is world readable though
Is there some trick that I'm missing here?
The container in question is still running on Proxmox 4.4 and it seems that fuse mounting is not supported and neither the mapping of uid's as per https://pve.proxmox.com/wiki/Unprivileged_LXC_containers#Using_local_directory_bind_mount_points
So I moved the container to a newer cluster (v6) and it all works fine there.
So I moved the container to a newer cluster (v6) and it all works fine there.