Error when mounting glusterfs mountpoint in inner container

First, thank you for bringing us Sysbox.

Description of the problem:

We are trying to test some glusterfs configuration using the following:

• Running 2 containers (from debian:bullseye), clientA and clientB, using sysbox-runc with docker and glusterfs client installed, with a glusterfs mountpoint at /srv/platform.
• Running two others containers as glusterfs servers (on runc since sysbox-runc prevent using extended attributes)

So far, so good all is working perfectly as expected.

Now we run an inner container inside clientA (or clientB), this container has a mounted volume (type bind) on a glusterfs mountpoint directory: the container fail to start with the following error :

> docker run -it --rm -v /srv/platform:/platform debian:bullseye

docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused:
process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/srv/platform" to rootfs at "/platform"
caused: change mount propagation through procfd: no such file or directory: unknown.

Note:

1. Binding a volume which is a glusterfs mountpoint mounted on bare metal host in a docker container (using runc) works without problem.
2. If we mount the parent directory of the glusterfs mountpoint, then we can access the mountpoint and it works as expected (i.e accessing replicated data)

Expected result

Beeing able to bind a glusterfs mountpoint in a sysbox running container into an inner container.

System configuration:

host: Ubuntu 18.04, kernel 5.0.4
container: debian:bullseye
sysbox-runc
edition: Community Edition (CE)
version: 0.4.1
commit: d540126188a1e8595c8f769aeb91833002c37b3a
built at: Fri Oct 1 19:33:49 UTC 2021
built by: Rodny Molina
oci-specs: 1.0.2-dev
docker/runc (host and container):
Docker version 20.10.12, build e91ed57
runc version 1.0.2
commit: v1.0.2-0-g52b36a2
spec: 1.0.2-dev
go: go1.16.10
libseccomp: 2.5.1

David.