> There may be some lag time before this is using the right image for OSE, but OKD should be good now.
Thanks! I change status to "MODIFIED" since it isn't ready for OCP.
One more question, how to check this image already based on the RHEL?
I want to check the "/etc/redhat-release" info but failed.
[root@dhcp-140-18 ~]# docker run --rm -ti --entrypoint="" quay.io/operatorframework/configmap-operator-registry:latest cat /etc/redhat-release
/usr/bin/docker-current: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"cat\": executable file not found in $PATH".
mac:ocp-31 jianzhang$ oc cp openshift-operators/installed-community-global-operators-7hq4f:/etc/redhat-release .
exec failed: container_linux.go:336: starting container process caused "exec: \"tar\": executable file not found in $PATH"
error: etc/redhat-release no such file or directory
Joel will take over on this bug now and see to it that it is added to our build data.
From conversation on slack just now
Nick Hale [10 minutes ago]
I’m pretty sure for downstream all binaries are being built into the `operator-registry` image.
Nick Hale [3 minutes ago]
yup just double-checked and our `image-references` configures a swap out for references of `quay.io/operatorframework/configmap-operator-registry:latest` with the image stream for `operator-registry`
ART is building operator-registry already from Dockerfile in https://github.com/operator-framework/operator-registry
Moving this bug back to OLM.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.