Recent content by a5m0deu5

cool just set this up fine using the guide!

cool just set this up fine using the guide!

looking forward to it :D

I just checked "service --status-all" and I don't see zed running, was this not implemented?

If it completes it will not have any output, go ahead and try to use fuse like you were before and see if it's erroring.

can you try running this command in your container as root? mknod -m 666 /dev/fuse c 10 229

I appear to be up to date via dist-upgrade (I'm not on testing repo) I just tried this fix in the container https://github.com/lxc/lxc/issues/80 # mknod -m 666 /dev/fuse c 10 229 looks like it's working now! Guess I just needed the combo of renaming cuse.ko on pve and adding the fuse node...

ok, but doing it on pve host still didn't make it work in the container, maybe I'm missing something basic? Tried rebooting pve host after copying cuse.ko to fuse.io and doing modprobe fuse on host but still not working in container :(

on pve host 'modprobe fuse' completes trying it in an ubuntu lxc container: # modprobe fuse modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/4.2.2-1-pve/modules.dep.bin' and I still get the same errors I posted above when trying to use...

Yes I made a copy modules/4.2.2-1-pve/kernel/fs/fuse# cp cuse.ko fuse.ko but trying to make an encfs mount errors with: fuse: device not found, try 'modprobe fuse' first fuse failed. Common problems: - fuse kernel module not installed (modprobe fuse) - invalid options -- see usage message...

is there a functioning work around to get fuse working in an lxc container? no movement on the bug report it seems

I just ran into this today trying to use fuse in an ubuntu lxc.... is there a fix to get this working?