anchor.diff:  [source,terminal]
   ----
   pids_limit = 2048
  +log_size_max = -1
   log_level = "debug"
   ----
  -+
  -[source,terminal]
  -----
  -$ head -n 7 /etc/containers/storage.conf
  +
  +.. Verify the changes in the `storage.conf`file:
  ++
  +[source,terminal]
  +----
  +sh-4.4# head -n 7 /etc/containers/storage.conf
   ----
   +
   .Example output
  
positive.code: spec:
   machineConfigPoolSelector:
     matchLabels:
       custom-crio: overlay-size
   containerRuntimeConfig:
     pidsLimit: 2048
     logLevel: debug
     overlaySize: 8G
  EOF
  ----
  
  . To apply the `ContainerRuntimeConfig` object settings, run:
  +
  [source,terminal]
  ----
  $ oc create -f /tmp/overlay-size
  ----
  
  . To verify that the settings wer applied, run:
  +
  [source,terminal]
  ----
  $ oc get ContainerRuntimeConfig
  NAME           AGE
  overlay-size   3m19s
  
  ----
  
  . To edit a pool of machines, such as `worker`, run the following command to open a machine config pool:
  +
  [source,terminal]
  ----
  $ oc edit machineconfigpool worker
  ----
  
  . Check that a new `containerruntime` object has appeared under the `machineconfigs`:
  +
  [source,terminal]
  ----
  $ oc get machineconfigs | grep containerrun
  99-worker-generated-containerruntime   2c9371fbb673b97a6fe8b1c52691999ed3a1bfc2  3.1.0  31s
  ----
  . Monitor the machine config pool as the changes are rolled into the machines until all are shown as ready:
  +
  [source,terminal]
  ----
  
negative.code: worker  rendered-worker-169  False    True      False     3             1                  1                    0                     9h
  ----
  
  . Verify that the settings were applied in CRI-O:
  
  .. Open an `oc debug` session to a node in the machine config pool and run `chroot /host`.
  +
  [source, terminal]
  ----
  $ oc debug node/<node_name>
  ----
  +
  [source, terminal]
  ----
  sh-4.4# chroot /host
  ----
  
  .. Verify the changes in the `crio.conf` file:
  +
  [source,terminal]
  ----
  sh-4.4# crio config | egrep 'log_level|pids_limit|log_size_max'
  ----
  +
  .Example output
  