[Users] fuse filesystem inside a container?

George Georgalis george at galis.org
Wed Aug 31 18:30:29 EDT 2011

On Wed, Aug 31, 2011 at 11:37 AM, George Georgalis <george at galis.org> wrote:
> On Wed, Aug 31, 2011 at 10:45 AM, Bogdan-Stefan Rotariu
> <bogdan at rotariu.ro> wrote:
> ...
>>> I'm able to make the md/fuse devices but I've been unable to configure
>>> a container to additionally include fuse filesystem capability.
>>> vzctl set $id --devices b:9:2:rw c:10:229:rw --save
>>> then after starting the containers,
>>> vzctl exec $id mknod /dev/fuse c 10 229
>>> vzctl exec $id mknod /dev/md2 b 9 2
>> [...]
>>> Fuse is being used to mount a gluster filesystem. Am I missing a step?
>> Yep,
>> Make sure you have the module in the container, kmod-fuse, and you can
>> load it.
> Well that is certainly confusing, since the container doesn't have its
> own kernel. What does loading a kernel in a container mean?
> The host has (and uses) the following modules:
> /lib/modules/2.6.18-238.19.1.el5.028stab092.2/extra/fuse.ko
> /usr/lib64/glusterfs/3.0.0/xlator/mount/fuse.so.0.0.0
> I presume fuse.ko is the one loaded by the kernel while the gluster
> client uses fuse.so.0.0.0 in userspace.
> In the container I have only,
> /opt/glusterfs/3.2.3/lib64/glusterfs/3.2.3/xlator/mount/fuse.so.0.0.0
> but when I try to load it I get:
> insmod: error inserting
> '/opt/glusterfs/3.2.3/lib64/glusterfs/3.2.3/xlator/mount/fuse.so.0.0.0':
> -1 Operation not permitted
> How do I load this fuse capability into the container?

I've identified the warnings/errors in my prior email as memory
allocation limits, so I set privvmpages to unlimited and reinstalled
fuse & fuse-libs in the container without issue.

However I still have the confounding issue of how to I make the fuse
filesystem available in the container /proc/filesystems like it is in
the host?


George Georgalis, (415) 894-2710, http://www.galis.org/

More information about the Users mailing list