I installed Sysbox v0.7.1 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 "da90ea28b8074d976b3dcb249e8b2f843709ec6decaf591104db2889c7e20e93": 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: write sysctl key net.ipv4.ip_unprivileged_port_start: write /proc/sys/net/ipv4/ip_unprivileged_port_start: permission denied
Sysbox version: v0.7.1
OS: Ubuntu 24.04
EKS Version: 1.35
Containerd version: v2 2.2.1
Kernel version: 6.17.0-1015-aws
AppArmor is enabled: kernel.apparmor_restrict_unprivileged_userns = 1
I installed Sysbox v0.7.1 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 "da90ea28b8074d976b3dcb249e8b2f843709ec6decaf591104db2889c7e20e93": 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: write sysctl key net.ipv4.ip_unprivileged_port_start: write /proc/sys/net/ipv4/ip_unprivileged_port_start: permission deniedSysbox version: v0.7.1
OS: Ubuntu 24.04
EKS Version: 1.35
Containerd version: v2 2.2.1
Kernel version: 6.17.0-1015-aws
AppArmor is enabled: kernel.apparmor_restrict_unprivileged_userns = 1