nestybox
Kubernetes 1.33 support
Sorry for my silly question as I am a newbie to sysbox, but what could be the compatibility issues to newer k8s versions? I am running sysbox on k8s v1.34. I have to mention that I am not using the sysbox daemonset.
Sorry for my silly question as I am a newbie to sysbox, but what could be the compatibility issues to newer k8s versions? I am running sysbox on k8s v1.34. I have to mention that I am not using the sysbox daemonset.
I only use the daemon set that the sysbox-deploy-k8s.sh script uses, and the supported versions are listed in the is_supported_k8s_version() function. But tbh, it might be possible to simply add v1.33 (and v1.34) there, but there could be compatibility issues with some libraries and other components used, right?
We just merged @sudermanjr's PR to add K8s 1.33 support. Please try it and let us know if any issues.
@rodnymolina can we make release candidate or release with 1.33 support. so that we can try in k8s cluster.
or any container image tag which we can use test the 1.33 support would be very helpful
Hello, current release and image sysbox-deploy-k8s:v0.6.7-0 used by daemonset are not working with k8s 1.33
k logs sysbox-deploy-k8s-vrpr8 ERROR: Sysbox is not supported on this Kubernetes version (v1.33).
Any estimation on getting it ready? there 1.34 already available everywhere...
We just merged @sudermanjr's PR to add K8s 1.33 support. Please try it and let us know if any issues.
Not working with GKE 1.33, giving ID map error "reading ID mappings from "/proc/0/uid_map": open /proc/0/uid_map: no such file or directory: CreateContainerError"
I'm not seeking a fix but I had to drop back to K8S 1.32, running on Ubuntu 22.04, before the sysbox-deploy-k8s would work. It didn't like any of the more recent Debian or Ubuntu versions and still claims "not supported" on K8S 1.33 and 1.34. For the various approaches (K8S vs Docker vs other), the docs could use some updating/culling.
We have upgraded AKS 1.32.* to 1.33.3 and receiving the above error ? Any pointers to resolve this ?
mappings from "/proc/0/uid_map": open /proc/0/uid_map: no such file or directory: CreateContainerError"
@ctalledo @sudermanjr @rodnymolina - Any updated for this issue, please?
Hello, current release and image sysbox-deploy-k8s:v0.6.7-0 used by daemonset are not working with k8s 1.33
k logs sysbox-deploy-k8s-vrpr8 ERROR: Sysbox is not supported on this Kubernetes version (v1.33).Any estimation on getting it ready? there 1.34 already available everywhere...
@artsiom-abakumov - Good morning. have you received any response? are you able to resolve issue from your end ?
@artsiom-abakumov - Good morning. have you received any response? are you able to resolve issue from your end ?
As i'm doing platform's POCs, for now I moved with alternatives solutions for workload isolation in kubernetes (kata, gvisor)...
@CursorRama12645 @pradeepmalji were either of you able to get past that error? It seems like turning off the feature gate UserNamespacesSupport will get rid of the "/proc/0/uid_map" error above
@CursorRama12645 @pradeepmalji were either of you able to get past that error? It seems like turning off the feature gate
UserNamespacesSupportwill get rid of the"/proc/0/uid_map"error above
Unable to turn off feature gate UserNamespacesSupport in GKE
Unable to turn off feature gate
UserNamespacesSupportin GKE
So u are still stuck
Unable to turn off feature gate
UserNamespacesSupportin GKESo u are still stuck
Yes
For those of you NOT on GKE or other managed K8s, we've disabled the UserNamespacesSupport feature gate and the daemon set is working on our 1.33 cluster.
We had to build the image from source though.
It seems that the only missing thing is a release. Any ETA on that ?
