Buildkit fails on AKSUbuntu-2204gen2containerd-202601.13.0 node pool version (`can't open cgroup: openat2 /sys/fs/cgroup/kubepods.slice/kubepods-besteffort.slice [...]: no such or directory: unknown`)

Contributing guidelines and issue reporting guide

• I've read the contributing guidelines and wholeheartedly agree. I've also read the issue reporting guide.

Well-formed report checklist

• I have found a bug that the documentation does not mention anything about my problem
• I have found a bug that there are no open or closed issues that are related to my problem
• I have provided version/information about my environment and done my best to provide a reproducer

Description of bug

Bug description

Buildkit fails on AKSUbuntu-2204gen2containerd-202601.13.0 node pool version

Reproduction

Deploy buildkit pod on a node which has AKSUbuntu-2204gen2containerd-202601.13.0
Probe will fail with below error
unable to start container process: error starting setns process: can't open cgroup: openat2 /sys/fs/cgroup/kubepods.slice/kubepods-besteffort.slice/kub │
│ epods-besteffort-pod88aea853_237f_476a_bd46_b1acbf24f80b.slice/cri-containerd-83018fe1ccbb98d1a44d9b42b9bb5ec1b88af5b5dcdd7ab1c611db3a147f89a3.scope: no such file or directory: unknown

Version information

Buildkit pod works fine on cluster which has AKSUbuntu-2204gen2containerd-202511.20.0.

difference between both nodepool is containerd version.

No source files or tests are named. Start by reproducing the BuildKit pod probe on AKSUbuntu-2204gen2containerd-202601.13.0 and comparing it with the working 202511.20.0 node pool, especially their containerd versions. Done means the probe starts successfully without the missing cgroup error.