shy mauve
I have a dagger container that uses glusterfs to mount folders.
The container runs this (the glusterfs-client has already been installed):
mkdir /mnt/glusterfs && \
mount -t glusterfs HOST:/path,HOST:/path,HOST:/path /mnt/glusterfs
This won't work inside of a dagger container. I believe this is because the container does not have access to the necessary kernel module (fuse) to do make filesystem changes. The closest setting I can find is experimentalPrivilegedNesting but that doesn't fix it.
┃ [2023-06-01 10:57:22.870360] I [MSGID: 100030] [glusterfsd.c:2715:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 5.5 (args: /usr/sbin/glusterfs --process-name fuse --volfile-server=<HOST> --volfil
┃ e-id=/titan /mnt/glusterfs)
┃ [2023-06-01 10:57:22.871163] E [mount.c:469:gf_fuse_mount] 0-glusterfs-fuse: cannot open /dev/fuse (No such file or directory)
┃ [2023-06-01 10:57:22.871192] E [MSGID: 101019] [xlator.c:715:xlator_init] 0-fuse: Initialization of volume 'fuse' failed, review your volfile again
Does dagger support adding capabilities to a container i.e. --cap-add=ALL or do I have to mount the folder on the host and then use withMountedDirectory ?