[lxc-users] FUSE stopped working inside containers

Serge E. Hallyn serge at hallyn.com
Wed Jul 13 14:12:31 UTC 2016

Quoting Saint Michael (venefax at gmail.com):
> ​​rpm -qa | grep lxc
> lxc-libs-1.1.5-1.fc22.x86_64
> lxc-1.1.5-1.fc22.x86_64
> Since the latest changes in ​LXC, I am out of business, since Fuse does not
> work anymore inside containers, and that is what I use for a
> line-of-production application that maps an FTP server to /mnt
>> ​fuse is loaded, which can be seen with
> lsmod | grep fuse
> ​but any attempt to do this
> curlftpfs ftp://ftp.xxxxx.com /mnt/ -o user=aaaaa:bbbbb
> fails with
> fuse: device not found, try 'modprobe fuse' first
> ​Note: it works on the host just fine, and it used to work fine in my
> containers until a few days ago.

Does /dev/fuse exist in the container?  You'd have to give some details
about the container (at least a config file) so we could see how /dev/fuse
is meant to be there.  But since it says "device not found" I suspect
the file is simply not there, rather than the container having lost
permissions to use it.  Perhaps you're using a persistent-till-next-reboot
dev mountpoint for the container and started the container before loading
fuse, so no /dev/fuse bind mount could be made?  Just guessing.


More information about the lxc-users mailing list