Cluster-logging-operator CreateContainerConfigError: container has runAsNonRoot and image will run as root

Description of problem:

Cluster-logging-operator CreateContainerConfigError: container has runAsNonRoot and image will run as root

Events:
  Type     Reason          Age                   From               Message
  ----     ------          ----                  ----               -------
  Normal   Scheduled       4m7s                  default-scheduler  Successfully assigned openshift-logging/cluster-logging-operator-54f77757dc-jxwkz to ip-10-143-1-78.ec2.internal by ip-10-143-1-31
  Normal   AddedInterface  4m5s                  multus             Add eth0 [10.129.2.38/23] from ovn-kubernetes
  Normal   Pulling         4m5s                  kubelet            Pulling image "registry.redhat.io/openshift-logging/cluster-logging-rhel8-operator@sha256:42c94e6fa2ced71be31255d43e85dfb2148439d2a99a57c0bacc8f5b7494ade1"
  Normal   Pulled          3m20s                 kubelet            Successfully pulled image "registry.redhat.io/openshift-logging/cluster-logging-rhel8-operator@sha256:42c94e6fa2ced71be31255d43e85dfb2148439d2a99a57c0bacc8f5b7494ade1" in 44.563293863s
  Warning  Failed          69s (x12 over 3m20s)  kubelet            Error: container has runAsNonRoot and image will run as root (pod: "cluster-logging-operator-54f77757dc-jxwkz_openshift-logging(82879320-baaa-4850-ba74-e443bc55be1c)", container: cluster-logging-operator)
  Normal   Pulled          69s (x11 over 3m19s)  kubelet            Container image "registry.redhat.io/openshift-logging/cluster-logging-rhel8-operator@sha256:42c94e6fa2ced71be31255d43e85dfb2148439d2a99a57c0bacc8f5b7494ade1" already present on machine

Version-Release number of selected component (if applicable):

Openshift 4.11

cluster-logging-rhel8-operator/images/v5.5.6-2

How reproducible:

Always

Steps to Reproduce:

1.  Deploy cluster-logging 5.5.6
2.  
3. ...