When switching the container runtime using a ContainerRuntimeConfig, conmon using the wrong,unupdated --root path for the runtime. 

    4.18.0-0.nightly-2024-12-20-221830

1.Apply containerRuntimeConfig requesting runc as the default runtime. apiVersion: machineconfiguration.openshift.io/v1
kind: ContainerRuntimeConfig
metadata:
  name: enable-runc-worker
spec:
  containerRuntimeConfig:
    defaultRuntime: runc
  machineConfigPoolSelector:
    matchLabels:
      machineconfiguration.openshift.io/role: worker

2. Wait for MCP to turn updated
3. oc debug the worker node
4. ps -ef | grep -E 'crun|runc'  

The last command will yield a list of processes like:
root     1230048       1  0 08:33 ?        00:00:00 /usr/bin/conmon -b /run/containers/storage/overlay-containers/9917f380f2e7a88cd8cf09023f13a7500014cd81cfd97213b29bcd35258f886d/userdata -c ........../userdata -r /usr/bin/runc --runtime-arg --root=/run/crun --socket-dir-path /var/run/crio --syslog -u 9917f380f2e7a88cd8cf09023f13a7500014cd81cfd97213b29bcd35258f886d -s -t  


Upon closer inspection, the --root=/run/crun value does not align with the -r /usr/bin/runc runtime specification.

All processes should be using runc with correct --root value:
root     1230048       1  0 08:33 ?        00:00:00 /usr/bin/conmon -b /run/containers/storage/overlay-containers/9917f380f2e7a88cd8cf09023f13a7500014cd81cfd97213b29bcd35258f886d/userdata -c ........../userdata -r /usr/bin/runc --runtime-arg --root=/run/runc --socket-dir-path /var/run/crio --syslog -u 9917f380f2e7a88cd8cf09023f13a7500014cd81cfd97213b29bcd35258f886d -s -t