Bidirectional Mount Propagation fail container creation
Open
@ctalledo is already working on this.
Since Jul 11, 2025.
bug
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
We are running cri-o + sysbox on kubernetes and getting an error jailing process inside rootfs caused: pivot_root invalid argument
when setting a volume mount propagation to bidirectional, would really appreciate it if we can get some support on this.
spec:
template:
metadata:
annotations:
io.kubernetes.cri-o.Devices: /dev/fuse
io.kubernetes.cri-o.userns-mode: "auto:size=65536"
spec:
runtimeClassName: sysbox-runc
volumes:
- name: fuse-mounts
hostPath:
path: /mnt/fuse-mounts
type: DirectoryOrCreate
containers:
- command:
- "/bin/sh"
- "-c"
- |
sleep infinity
image: buildbarn-worker:xxx
imagePullPolicy: IfNotPresent
name: app
resources:
requests:
cpu: "4"
memory: 31Gi
limits:
memory: 31Gi
volumeMounts:
- name: fuse-mounts
mountPath: /mnt/fuse-mounts
mountPropagation: Bidirectional
securityContext:
privileged: true
- command: ["sleep", "infinity"]
image: buildbarn-worker:xxx
imagePullPolicy: IfNotPresent
name: buildbarn
resources:
requests:
cpu: "1"
memory: 3Gi
limits:
memory: 3Gi
volumeMounts:
- name: fuse-mounts
mountPath: /mnt/fuse-mounts
mountPropagation: HostToContainer
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.