Description of problem: When we try to deploy logging on Openshift 3.7 using image registry.access.redhat.com/openshift3/logging-curator:v3.7 it finished on CreateContainerConfigError and showning an error identifying user to start container: 3m 1m 10 kubelet, servername.serverdomain spec.containers{curator} Warning Failed Error: container has runAsNonRoot and image has non-numeric user (nobody), cannot verify user is non-root Version-Release number of selected component (if applicable): 3.7.23 How reproducible: Always, when "runAsNonRoot" Steps to Reproduce: 1. Try to deploy logging in an OCP 3.7 cluster. Actual results: Curator container does not start due to: "Error: container has runAsNonRoot and image has non-numeric user (nobody), cannot verify user is non-root" Expected results: Curator container started normally. Image should be generated using a numeric user as stated in https://docs.openshift.com/container-platform/3.9/creating_images/guidelines.html#openshift-specific-guidelines Additional info: Variables passed to the playbook: openshift_logging_install_logging=true openshift_logging_storage_kind=nfs openshift_logging_storage_access_modes=['ReadWriteOnce'] openshift_logging_storage_nfs_directory=/exports openshift_logging_storage_nfs_options='*(rw,root_squash)' openshift_logging_storage_volume_name=logging openshift_logging_storage_volume_size=10Gi openshift_logging_storage_labels={'storage': 'logging'} openshift_logging_kibana_hostname=hostname.domain openshift_logging_es_cluster_size=1 openshift_logging_image_prefix=registry.access.redhat.com/openshift3/
This was fixed in a consequent curator release. The latest v3.7.z curator tag as of now is v3.7.42-2[1]. Please advice the customer to upgrade. [1]https://access.redhat.com/containers/#/registry.access.redhat.com/openshift3/logging-curator/images/v3.7.42-2