Description of problem: In our https://docs.openshift.com/container-platform/4.2/operators/olm-restricted-networks.html, "Create an Operator catalog image" section. We used this "openshift/origin-base" as a base image, but it's too old. We should update it. mac:~ jianzhang$ docker images|grep origin-base quay.io/openshift/origin-base latest 22e2204edf0b 3 weeks ago 227MB openshift/origin-base latest f779ab8af41a 9 months ago 224MB Version-Release number of selected component (if applicable): 4.2 How reproducible: always Steps to Reproduce: 1. Check the origin-base image. Compare it with another one in Quay. Actual results: This openshift/origin-base is too old, it should come from registry.redhat.io IIUC. Expected results: We should update it. Additional info: https://access.redhat.com/containers/?tab=images#/registry.access.redhat.com/ubi7/ubi
Here's a docs PR to update to the newer downstream image. The image built fine for me, though not sure how much more testing it needs. https://github.com/openshift/openshift-docs/pull/19036 @Jian - WDYT?
Hi, Alex Thanks! @Shwan could you help review it? Thanks!
And should we leave it tagless or specify one? Note these instructions would only be for OCP 4.2, as we don't need to provide the Dockerfile in 4.3+.
Setting target release to the active development branch (4.4). For fixes, if any, which require backport to prior versions, clones of this BZ will be created.
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. https://access.redhat.com/errata/RHBA-2020:0581