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: [id="create-a-containerruntimeconfig_{context}"]
  = Creating a `ContainerRuntimeConfig` CR to edit CRI-O parameters
  
  The `ContainerRuntimeConfig` custom resource definition (CRD) provides a structured way of changing settings associated with the {product-title} CRI-O runtime. Using a `ContainerRuntimeConfig` custom resource (CR), you select the configuration values you want and the MCO handles rebuilding the `crio.conf` and `storage.conf` configuration files.
  
  Parameters you can set in a `ContainerRuntimeConfig` CR include:
  
  * **PIDs limit**: Sets the maximum number of processes allowed in a container. By default, the limit is set to 1024 (`pids_limit = 1024`).
  * **Log level**: Sets the level of verbosity for log messages. The default is `info` (`log_level = info`). Other options include `fatal`, `panic`, `error`, `warn`, `debug`, and `trace`.
  * **Overlay size**: Sets the maxim size of a container image. The default is 10 GB.
  * **Maximum log size**: Sets the maximum size allowed for the container log file. The default maximum log size is unlimited (`log_size_max = -1`). If it is set to a positive number, it must be at least 8192 to not be smaller than  the `conmon` read buffer. Conmon is a program that
  monitors communications between a container manager (such as Podman or CRI-O) and the OCI runtime (such as runc or crun) for a single container.
  
  The following procedure describes how to change CRI-O settings using the `ContainerRuntimeConfig` CR.
  
  .Procedure
  
  . To raise the `pidsLimit` to 2048, set the `logLevel` to `debug`, and set the `overlaySize` to 8 GB, create a CR file (for example, `overlay-size.yaml`) that contains that setting:
  +
  [source,yaml]
  ----
  $ cat << EOF > /tmp/overlay-size.yaml
  apiVersion: machineconfiguration.openshift.io/v1
  kind: ContainerRuntimeConfig
  metadata:
  
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
  