Jupyterlab spawns fails due to cgroup error


We are seeing a weird problem where spawning jupyterlab fails due to the following error:
2023-11-29T18:37:13Z [Warning] Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: unable to set memory limit to 6144 (current usage: 2535424, peak usage: 3141632): unknown

Has anyone seen this? What could be the issue? Is there anything cgroup related in jupyterhub helm chart that sets cgroups configs?

Response from k8s slack community: Slack

Any help will be appreciated!

It doesn’t sound like something specific to the Z2JH Helm chart. Are you using the default configuration or have you customised your deployment? Are you using one of the standard singleuser images?

That requires a login, can you share the response here?

Thank you for your response! Figured out that the problem was with how we were setting memory resource limits and requests and not with the helm chart.

Error from the spawning was pointing that the request resource the pod was making, was well below the minimum threshold and hence the spawn was failing. By making sure that we are passing correct resource request and limits fixed the problem.