Sysbox Team,
We are running sysbox across multiple AKS Clusters in our Enterprise. We have a mix of Shared and Dedicated AKS clusters.
Lately we are having issues with the Version compatibility for Sysbox installed across our AKS Clusters and is a major blocker as we run github runners on AKS clusters that is used by multiple application teams within the org. This leads us to look for alternatives for sysbox.
We can see that the Latest Version of Sysbox is V0.7.0 - https://github.com/nestybox/sysbox/releases
We are encountering below Scenarios across our Clusters:
Currently, we are utilizing Sysbox v0.6.7-0, which is only compatible with AKS cluster version 1.32.11. Although our clusters are currently on version 1.35, we intend to upgrade to 1.36.X
Scenario 1: Upgrading the cluster while maintaining the nodepool at 1.32.11
Attempts to upgrade the cluster to the latest version failed. The system reported an incompatibility error as below
"Node pool version 1.32.11 and control plane version 1.36.1 are incompatible. Minor version of node pool cannot be more than 3 versions less than control plane's version. Minor version of node pool is 32 and control plane is 36."
Scenario 2: Upgrading the sysbox nodepool to 1.33.x
When upgrading the nodepool to version 1.33.x, the daemonset pods failed. The error message indicated that Sysbox does not support Kubernetes version v1.35.
"Sysbox is not supported on this Kubernetes version (v1.35)."
Scenario 3: Upgrading to the latest Sysbox pre-release (0.7.0-0)
After updating to the newest pre-release based on the release documenthttps://github.com/nestybox/sysbox/releases#release-v0.7.0
pod got failed with below error
Error: reading ID mappings from "/proc/0/uid_map": open /proc/0/uid_map: no such file or directory
Further investigation reveals that AKS versions 1.33.x and above utilize Ubuntu 24.04. The kernel features in this OS differ significantly from Ubuntu 22.04, which functioned correctly in AKS 1.32.x.
So sysbox on functions correctly on our AKS clusters where the sysbox node pool version is 1.32.XXX and AKS control plane is at 1.35.XXX
If we upgrade AKS Control Plan to 1.36.XXX then we also have to upgrade sysbox nodepool to version 1.33.XXX to maintain the N-3 support versions.
Sysbox does not function on AKS versions at 1.33.XXX
Would Appreciate any help on this issue.
Sysbox Team,
We are running sysbox across multiple AKS Clusters in our Enterprise. We have a mix of Shared and Dedicated AKS clusters.
Lately we are having issues with the Version compatibility for Sysbox installed across our AKS Clusters and is a major blocker as we run github runners on AKS clusters that is used by multiple application teams within the org. This leads us to look for alternatives for sysbox.
We can see that the Latest Version of Sysbox is V0.7.0 - https://github.com/nestybox/sysbox/releases
We are encountering below Scenarios across our Clusters:
Currently, we are utilizing Sysbox v0.6.7-0, which is only compatible with AKS cluster version 1.32.11. Although our clusters are currently on version 1.35, we intend to upgrade to 1.36.X
Scenario 1: Upgrading the cluster while maintaining the nodepool at 1.32.11
Attempts to upgrade the cluster to the latest version failed. The system reported an incompatibility error as below
"Node pool version 1.32.11 and control plane version 1.36.1 are incompatible. Minor version of node pool cannot be more than 3 versions less than control plane's version. Minor version of node pool is 32 and control plane is 36."
Scenario 2: Upgrading the sysbox nodepool to 1.33.x
When upgrading the nodepool to version 1.33.x, the daemonset pods failed. The error message indicated that Sysbox does not support Kubernetes version v1.35.
"Sysbox is not supported on this Kubernetes version (v1.35)."
Scenario 3: Upgrading to the latest Sysbox pre-release (0.7.0-0)
After updating to the newest pre-release based on the release documenthttps://github.com/nestybox/sysbox/releases#release-v0.7.0
pod got failed with below error
Error: reading ID mappings from "/proc/0/uid_map": open /proc/0/uid_map: no such file or directory
Further investigation reveals that AKS versions 1.33.x and above utilize Ubuntu 24.04. The kernel features in this OS differ significantly from Ubuntu 22.04, which functioned correctly in AKS 1.32.x.
So sysbox on functions correctly on our AKS clusters where the sysbox node pool version is 1.32.XXX and AKS control plane is at 1.35.XXX
If we upgrade AKS Control Plan to 1.36.XXX then we also have to upgrade sysbox nodepool to version 1.33.XXX to maintain the N-3 support versions.
Sysbox does not function on AKS versions at 1.33.XXX
Would Appreciate any help on this issue.