Naoki MATSUMOTO

All tests have passed

適当に動かしてみます

RClone seems to use fuse, so it will work with meta-fuse-csi-plugin. https://github.com/rclone/rclone/blob/91b11f9eac51b58e03bd1954e258e4a5c575f92e/cmd/mount/mount.go#L3

It seems fuse-overlayfs calls low-level api `fuse_session_mount` and it calls fusermount3 in `fuse_kern_mount`. https://github.com/containers/fuse-overlayfs/blob/18f4d6768ab2178f0147c1bac0ccfd7d44841a56/main.c#L5883C7-L5883C25 https://github.com/libfuse/libfuse/blob/3f6cf537b77597d89bebd8387e93d4e42428b966/lib/fuse_lowlevel.c#L3179 I think this plugin can mount fuse-overlayfs, but its mount destination is statically defined in...

Thank you for opening the first issue! rar2fs seems to use libfuse, so "fusermount3-proxy" mount approach should work. fusermount3-proxy approach is configured by injecting dedicated fusermount3-proxy binary to rar2fs container...

I think meta-fuse-csi-plugin works with rar2fs, and examples will help you to write manifest. If you have problems, could you reopen this issue and provide error details?

I've never tried bypass4netns with nested containers. This problem seems interesting. bypass4netns may wrongly hook syscalls and bypass sockets. I'll investigate this issue.

I confirmed the issue. bypass4netns handles sockets created in nested netns in the container's netns. This behavior is not expected and bypass4netns should handle only processes with container's netns, not...

Theoretically, the multi-node bypass can handle pod-to-pod communications without the proxy. bypass4netns can expose the pod's ports on the node by bypassing the socket when `bind(2)` called, and other pods...

> this still does not seem to fix Thanks, the issue seems to stem from other reasons. I'm going to investigate this issue with Usernetes environment. > this PR disables...