The image-registry pods are failing to start with the below error
~~~
13m Warning Failed pod/image-registry-779d9b979-jmlss Error: kubelet may be retrying requests that are timing out in CRI-O due to system load. Currently at stage container volume configuration: context deadline exceeded: error reserving ctr name k8s_registry_image-registry-779d9b979-jmlss_openshift-image-registry_5518d82d-0d4b-4820-8f8b-1b211be0f7dc_0 for id 39026bd511a3f603bf39997df0fecf091a375dcb9f7d876599a8870f18e7f983: name is reserved
~~~

Error occurs regardless the node the pods are scheduled on.
Load on the nodes is very low, ~10%
Nodes are very large
allocatable:
cpu: 63500m
ephemeral-storage: "429480772100"
memory: 526639896Ki

Looks like it is related to selinux relabel [1] but not sure how to apply any of the workarounds as the operator will revert any changes to the deployment.

How can we skip relabel to get the pods to start, if relabel is the issue?