Description of problem: Now, we ship the opm to the customer via the operator-registry image, but the opm extracted from the release image cannot work. [root@preserve-olm-env data]# ./opm version ./opm: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./opm) Version-Release number of selected component (if applicable): 4.6 How reproducible: always Steps to Reproduce: 1. Pull the release 4.6 operator-registry image [root@preserve-olm-env data]# docker pull registry.redhat.io/openshift4/ose-operator-registry:v4.6 v4.6: Pulling from openshift4/ose-operator-registry fecf0868d374: Already exists f7db571f3a05: Already exists 0c983affa284: Already exists fbcb77c49896: Pull complete c0169689d717: Pull complete Digest: sha256:938cd1e7bcdea01e06a63a507ae0f5eff2fbfc14ed1c2921a3667210d0c94f2a Status: Downloaded newer image for registry.redhat.io/openshift4/ose-operator-registry:v4.6 registry.redhat.io/openshift4/ose-operator-registry:v4.6 2. Extract the opm [root@preserve-olm-env data]# docker create registry.redhat.io/openshift4/ose-operator-registry:v4.6 d0f94503b5f9b2dc5958e118faca7a68fc32ad4fdfe7e9214b3fd28649d86f1b [root@preserve-olm-env data]# docker cp d0f94503b5f9b2dc5958e118faca7a68fc32ad4fdfe7e9214b3fd28649d86f1b:/bin/opm . 3. Run the opm. Actual results: [root@preserve-olm-env data]# ./opm version ./opm: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./opm) Expected results: The extracted opm can work well. Additional info: I also tried the current 4.7 operator-registry image, get the same error, as follows: [root@preserve-olm-env data]# oc adm release info registry.ci.openshift.org/ocp/release:4.7.0-0.nightly-2021-01-19-095812 |grep operator-registry operator-registry sha256:56493169715122404a9007e9c087ba36a5851f0cbccebd82c2c0a162ef80fdef [root@preserve-olm-env data]# podman pull --authfile .dockerconfigjson quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:56493169715122404a9007e9c087ba36a5851f0cbccebd82c2c0a162ef80fdef Trying to pull quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:56493169715122404a9007e9c087ba36a5851f0cbccebd82c2c0a162ef80fdef... Getting image source signatures Copying blob 4d7b928f7705 skipped: already exists Copying blob cca21acb641a skipped: already exists Copying blob d9e72d058dc5 skipped: already exists Copying blob b30858549dbb skipped: already exists Copying blob e9f724faf3c8 [--------------------------------------] 0.0b / 0.0b Copying config ecbb26b6cc done Writing manifest to image destination Storing signatures ecbb26b6ccc14c4b01f7c301cf16802ff9b11e20bac253e65bde1614cc609a42 [root@preserve-olm-env data]# podman create quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:56493169715122404a9007e9c087ba36a5851f0cbccebd82c2c0a162ef80fdef 9ed9dce7327ba5bbf8c83a4cba25b3742367f0e491dc22ef5ba1dc4dccdb278b [root@preserve-olm-env data]# rm -f ./opm [root@preserve-olm-env data]# podman cp 9ed9dce7327ba5bbf8c83a4cba25b3742367f0e491dc22ef5ba1dc4dccdb278b:/bin/opm . [root@preserve-olm-env data]# ./opm version ./opm: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./opm)
Version 2.28+ of glibc is documented as a prerequisite for the opm binary included in the release image (https://docs.openshift.com/container-platform/4.6/cli_reference/opm-cli.html#olm-installing-opm_opm-cli). I'm going to mark this as a duplicate of the issue that tracked the documentation change. I don't believe there is any plan to provide a pre-2.28-compatible opm binary downstream at this time. *** This bug has been marked as a duplicate of bug 1892004 ***
I think it still for RHEL8 only.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days