cluster-logging-operator ends up in CreateContainerConfigError: container has runAsNonRoot and image will run as root

cluster-logging-operator ends up in CreateContainerConfigError: container has runAsNonRoot and image will run as root.


  - image: registry.redhat.io/openshift-logging/cluster-logging-rhel8-operator@sha256:42c94e6fa2ced71be31255d43e85dfb2148439d2a99a57c0bacc8f5b7494ade1
    imageID: ""
    lastState: {}
    name: cluster-logging-operator
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        message: 'container has runAsNonRoot and image will run as root (pod: "cluster-logging-operator-78cc445466-c9r7n_openshift-logging(6b75f524-64c7-46ef-9256-036213a008bc)",
          container: cluster-logging-operator)'
        reason: CreateContainerConfigError

4.12.0-rc.4
local-storage-operator-metadata-container-v4.12.0.202212071935.p0.gbc3f9b7.assembly.stream-1

100%

1. Deploy cluster logging operator on a disconnected SNO environment from local-storage-operator-metadata-container-v4.12.0.202212071935.p0.gbc3f9b7.assembly.stream-(we are building a custom index image catalog source including this bundle)

2. Check cluster-logging-operator pod status:

oc -n openshift-logging get pods cluster-logging-operator-78cc445466-c9r7n  
NAME                                        READY   STATUS                       RESTARTS   AGE
cluster-logging-operator-78cc445466-c9r7n   0/1     CreateContainerConfigError   0          112m
 

Pod reports CreateContainerConfigError. Attaching the output of pod yaml.

Operator runs without errors.