:~# sshfs email@example.com:/var/lib/vz/dump/ /mnt/lala/
fuse: device not found, try 'modprobe fuse' first
:~# modprobe fuse
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.2.6-1-pve/modules.dep.bin'
...back to #12 of the thread, just that the err now is line 557 instead of 556 in ../libkmod/libkmod.c
Using fuse inside the container is problematic as fuse and the kernel freezer mechanism don't work together. If you really absolutely need to use fuse mounts inside a container, don't try to use snapshot backups or lxc-freeze on those containers, or you will end up with hanging containers. A possible alternative would be to establish the fuse mount on the host, and then bind mount it into the container with an mpX entry in the container config, but this is not well tested (feedback welcome, as always!).
well, after 1 restart i lost my fuse system, cuase it must be rebuilt every start, i was doing it so i could connect the different nodes i have into a single folder structure using sshfs on top of fuse, and that worked great, til i restarted.
Im literally considering writing my own solution in php or something and use ssh to put the actual sync together.
syncing files between nodes is hard.
and to help people and the staff here, given the glue that holds things together, staff is corrent about fuse and proxmox, not worth the trouble.
Proxmox is a life saver, Fuse is a cute toy.