Making Sysbox work with k8s 1.33 #987
Description
v0.6.7 previously worked with AL2023 EKS 1.32.
With AL2023 EKS 1.33.5 I can't get Sysbox to work.
Tried both v0.6.7 and master.
Installing using a custom script derived from the Daemonset.
When using CRIO I have been building the latest 1.33 branch of CRIO (1.33.8) + Sysbox patch.
Without any changes on the node I get, ""reading ID mappings from "/proc/0/uid_map": open /proc/0/uid_map: no such file or directory: CreateContainerError"
Disabling UsernameSpaceSupport on the node fixes the, "reading ID mappings from "/proc/0/uid_map": open /proc/0/uid_map: no such file or directory: CreateContainerError". However, PVCs get permission denied errors on writes making this unusable for us.
Tried master + UsernameSpaceSupport enabled + containerd and get an "aws cni can't get IP address" error (I don't get this error with flannel in a lima VM with AL2023.)
Going to try master + UsernamespaceSupport enabled + CRIO (without the auto userns annotation on the pod) to see if it somehow behaves differently.
Has anyone cracked the Contra code for getting Sysbox to work on EKS 1.33?
Ideally I'd love to have Sysbox work with containerd, but I'll settle for CRIO as long as it works.
If you got it to work with EKS and v1.33, please share what works for you. Thanks!