moby/buildkitd container crashing and health check error

[MShawNYSED]

I am working on a deployment pipeline and including a buildkitd service deployed to a kubernetes cluster. On a previous platform, this was accomplished and builds were happening without issue. However, the underlying infrastructure had to switch, and I am now faced with an issue I am not sure how to proceed with, as it appears to come from a deeper layer of containerization.

Symptom:
A singular moby/buildkitd:master (and versions back to v.0.17.0) pod is failing to successfully run. Any attempts to kubectl exec into the container cause an immediate crash of the container. The health/readiness checks in the pod definition also cause errors with the following event:

Warning Unhealthy 3m57s (x3584 over 21h) kubelet Readiness probe errored: rpc error: code = Unknown desc = command error: error opening file /sys/fs/cgroup/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod3cf10efa_2f7e_4db3_aa74_161eeda5a957.slice/crio-731260d274e77850b09a46046ccd20da14edce5518ac7684d720f0d508138ced.scope/container/cgroup.freeze: No such file or directory
, stdout: , stderr: , exit code -1

From the node, I can see the filesystem does not contain the crio-XXXXX/container directory.

Environment:
Oracle Linux 9 (Red Hat Enterprise Linux release 9.5 (Plow))

Installed Packages
cri-o.x86_64 1.31.5-150500.1.1
kubeadm.x86_64 1.31.6-150500.1.1
kubectl.x86_64 1.31.6-150500.1.1
kubelet.x86_64 1.31.6-150500.1.1
kubernetes-cni.x86_64 1.5.1-150500.1.1

Any and all help appreciated on figuring this out.

[eve0415]

Same issue here. Using Oracle Linux 9. Previously I was using Ubuntu and it was working fine.
It might be related with the OS or cri-o version changes.