How to make gcsfuse mounted path accessible by other container on same pod

containersgcsfusemount

Our goal is to use gcsfuse to mount a google bucket content to some path, and share this path with rest of the pod
So I tried to run our initContainer as privilege mode to run gcsfuse to mount bucket to our path1, inside of this initcontainer, I can see the content when doing ls -l that $path1

However, if I claim this path1 as the VolumnMounts and Volumn, other container cannot see the content under that path1

Unless I am following the example https://github.com/ageapps/k8s-storage-buckets/tree/master/gcsfuse-init to copy to some other folder and mount that folder as VolumnMount

But copying is not our preference, do we have a better way?

Best Answer

I am not running it in Kubernetes just straight up containers on a gcp vm. In order to see the mounts from the gcsfuse container, I needed to also run the second container with the --privileged --cap-add SYS_ADMIN options.

Also when launching my fuse container I shared the mount back to the host by adding this flag --device /dev/fuse -v /data:/data:shared.

Hopefully that will help you as there is not that much info about running gcsfuse in containers.

Related Solutions

Linux – Port inside linked docker container is not accessible to the other container

The host is a fedora 22 and it seems the firewall on host was preventing the containers to reach each other. I had Fedora's firewalld running, and that let containers ping each other but not reach their ports. I disabled firewalld, used only iptables instead, and with iptables containers could not even ping each other. If this is the fault of Docker added rules or the existing firewall rules, I haven't investigated yet. But stopping both firewalld and iptables on host made it work.

How to make a drive mount avaialble inside a container

You can use fstab to declare mount points using:

lxc.mount = /PATH/TO/fstab

This is an extension to LXC's config file. I usually put them together, outside the container's rootfs. Then, inside that fstab, you put entries like the normal /etc/fstab but the mount point is relative to the container's rootfs. For example:

/mnt/psql mnt/psql none bind,rw 0 0

See you!

Best Answer

Related Solutions

Linux – Port inside linked docker container is not accessible to the other container

How to make a drive mount avaialble inside a container

Related Topic