I did work around it by mounting the ftp site on the host and sharing /mnt with the container, but as a solution is poor, since I cannot execute the mound command from the container, to be run on the host. This was working fine until last week. I just checked and /dev/fuse does not exist in the container, although the module fuse is loaded. So the question is how do I create that device on the container
lxc.mount.entry = /mnt mnt none bind 0 0 lxc.tty = 10 lxc.pts = 1024 lxc.cgroup.devices.deny = a lxc.cgroup.devices.allow = c 1:3 rwm lxc.cgroup.devices.allow = c 1:5 rwm lxc.cgroup.devices.allow = c 5:1 rwm lxc.cgroup.devices.allow = c 5:0 rwm lxc.cgroup.devices.allow = c 4:0 rwm lxc.cgroup.devices.allow = c 4:1 rwm lxc.cgroup.devices.allow = c 1:9 rwm lxc.cgroup.devices.allow = c 1:8 rwm lxc.cgroup.devices.allow = c 136:* rwm lxc.cgroup.devices.allow = c 5:2 rwm lxc.cgroup.devices.allow = c 254:0 rwm lxc.cgroup.devices.allow = c 10:137 rwm # loop-control lxc.cgroup.devices.allow = b 7:* rwm # loop* lxc.mount.auto = cgroup lxc.kmsg = 0 lxc.cap.drop = lxc.utsname = centos7 lxc.autodev = 1 lxc.aa_profile = unconfined On Wed, Jul 13, 2016 at 10:12 AM, Serge E. Hallyn <[email protected]> wrote: > Quoting Saint Michael ([email protected]): > > 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. > > -serge > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
