Rook (ceph) fails to start correctly after upgrading to runc 1.2.0

Description

Rook (Ceph) fails starting correctly after upgrading to runc v1.2.0. Rolling back to runc v1.1.15 fixes all errors.

Steps to reproduce the issue

1. Install rook operator v1.15.3 in kubernetes cluster (on-prem) based upon Kubernetes v1.30.5
2. Everything works
3. Upgrade runc to v1.2.0
4. rook fails with errors:
   rook-ceph rook-ceph-mds-k8sfs-a-65588bd59d-d9ccf 1/2 CrashLoopBackOff 215 (53s ago) 19h
   rook-ceph rook-ceph-mds-k8sfs-b-686bdc8d8d-kk498 1/2 CrashLoopBackOff 67 (50s ago) 5h56m
   rook-ceph rook-ceph-mgr-b-58f9d6576b-4df8v 2/3 CrashLoopBackOff 333 (51s ago) 19h

I checked the output of kubectl describe nodes. There was no memory or storage pressure on the nodes.

Describe the results you received and expected

rook starting just like under runc v1.1.15

What version of runc are you using?

v1.1.15 (I rolled back from v1.2.0 and Everything works again).

Host OS information

PRETTY_NAME="Ubuntu 24.04.1 LTS"

Host kernel information

Linux 6.8.0-47-generic #47-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 21:40:26 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
(on all Kubernetes nodes).

Reproduce the failure with Rook operator v1.15.3 on Kubernetes v1.30.5, comparing runc v1.1.15 and v1.2.0 on Ubuntu 24.04.1 with the listed kernel. Start by collecting the affected pod status and failure details, then identify what changes between the two runc versions; done means Rook starts correctly under runc v1.2.0 or the incompatibility is clearly documented.