verified!

$ oc get clusterversion 
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2022-01-17-032357   True        False         71m     Cluster version is 4.7.0-0.nightly-2022-01-17-032357

$ oc get containerruntimeconfig  overlay-size -o yaml
...
spec:
  containerRuntimeConfig:
    logLevel: debug
    overlaySize: 9G
  machineConfigPoolSelector:
    matchLabels:
      custom-crio-overlay: overlay-size
...

$ oc get pod
NAME                                                             READY   STATUS    RESTARTS   AGE
hello-pod-1                                                      1/1     Running   0          12m

$ oc rsh hello-pod-1
# df -h 
Filesystem      Size  Used Avail Use% Mounted on
overlay         9.0G   12K  9.0G   1% /
tmpfs            64M     0   64M   0% /dev
tmpfs           7.4G     0  7.4G   0% /sys/fs/cgroup
shm              64M     0   64M   0% /dev/shm
tmpfs           7.4G   48M  7.3G   1% /etc/hostname
/dev/sda4       128G  8.2G  120G   7% /etc/hosts
tmpfs           7.4G   28K  7.4G   1% /run/secrets/kubernetes.io/serviceaccount
tmpfs           7.4G     0  7.4G   0% /proc/acpi
tmpfs           7.4G     0  7.4G   0% /proc/scsi
tmpfs           7.4G     0  7.4G   0% /sys/firmware
# exit

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.42 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0283