Sysbox v0.7.0 fails on Ubuntu 24.04 with kernel 6.x and containerd v2
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
I installed Sysbox v0.7.0 on Ubuntu 24.04 EKS worker nodes . The installation completes successfully, but any pod configured to use the sysbox-runc RuntimeClass fails to start.
Pods using the default runtime start successfully. The issue only occurs when using the Sysbox runtime.
Below is the error message
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox "e73c470a8c46b14c3c4ec6335d5e75dcbb5b1972f84ea458d06426db705c658a": failed to create containerd task: failed to create shim task: OCI runtime create failed: container_linux.go:439: starting container process caused: process_linux.go:608: container init caused: rootfs_linux.go:76: setting up rootfs mounts caused: rootfs_linux.go:1276: mounting "sysfs" to rootfs "/run/containerd/io.containerd.runtime.v2.task/k8s.io/e73c470a8c46b14c3c4ec6335d5e75dcbb5b1972f84ea458d06426db705c658a/rootfs" at "sys" caused: mount through procfd: operation not permitted
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox "774d244c8fe34bf7ef7f6e63cccc1026db2c8f581892ffbf14106c8e3d8e0e42": failed to create containerd task: failed to create shim task: OCI runtime create failed: container_linux.go:439: starting container process caused: process_linux.go:608: container init caused: rootfs_linux.go:76: setting up rootfs mounts caused: rootfs_linux.go:1276: mounting "sysfs" to rootfs "/run/containerd/io.containerd.runtime.v2.task/k8s.io/774d244c8fe34bf7ef7f6e63cccc1026db2c8f581892ffbf14106c8e3d8e0e42/rootfs" at "sys" caused: mount through procfd: operation not permitted
Sysbox version: v0.7.0-0
OS: Ubuntu 24.04
EKS Version: 1.35
Containerd version: v2 2.2.1
Kernel version: 6.17.0-1019-aws
AppArmor is enabled: kernel.apparmor_restrict_unprivileged_userns = 1
The issue is reproducible for every pod using the sysbox-runc RuntimeClass. Please let me know if any additional logs or diagnostics would help with troubleshooting.
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.
Research direction
Reproduce a pod using the sysbox-runc RuntimeClass on the stated Ubuntu 24.04 EKS environment, then compare it with a pod using the default runtime. Start from the reported mount through procfd: operation not permitted failure and collect any additional diagnostics requested in the issue. Done means the compatibility cause is confirmed and a concrete resolution or required configuration is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, linux, ubuntu
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100