Description of problem: Driver builds end with build error: error determining starting point for build: no FROM statement found Special Resource Controller manager pod shows this error in log: open /mnt/host/registries.conf: no such file or directory Version-Release number of selected component (if applicable): 4.10 How reproducible: Install Special Resource Operator from OLM and deploy a new specialresource. Steps to Reproduce: 1.Install SRO from OLM 2.Deploy a new SR
Tested on 4.10.24 and the bug is not fixed. The builds fail with: Pulling image as ... Resolving "as" using unqualified-search registries (/var/run/configs/openshift.io/build-system/registries.conf) Trying to pull registry.redhat.io/as:latest... time="2022-07-21T11:10:29Z" level=warning msg="failed, retrying in 1s ... (1/3). Error: initializing source docker://registry.redhat.io/as:latest: reading manifest latest in registry.redhat.io/as: unknown: Not Found" time="2022-07-21T11:10:30Z" level=warning msg="failed, retrying in 2s ... (2/3). Error: initializing source docker://registry.redhat.io/as:latest: reading manifest latest in registry.redhat.io/as: unknown: Not Found" time="2022-07-21T11:10:32Z" level=warning msg="failed, retrying in 4s ... (3/3). Error: initializing source docker://registry.redhat.io/as:latest: reading manifest latest in registry.redhat.io/as: unknown: Not Found" Trying to pull registry.access.redhat.com/as:latest... Trying to pull quay.io/as:latest... Trying to pull docker.io/library/as:latest... Warning: Pull failed, retrying in 5s ... This is because a line like "FROM $VAR as builder" in the Dockerfile would be evaluated as "FROM as" and of course there is no such image as "as". I could also see in the operator's logs: 1.6584117332418435e+09 INFO warning OnError: cannot extract manifest: could not build crane options: could not find a pull source for "quay.io/openshift-release-dev/ocp-release@sha256:e40e49d722cb36a95fa1c03002942b967ccbd7d68de10e003f0baa69abad457b": could not find registry for image "quay.io/openshift-release-dev/ocp-release@sha256:e40e49d722cb36a95fa1c03002942b967ccbd7d68de10e003f0baa69abad457b": loading registries configuration "/mnt/host/registries.conf": open /mnt/host/registries.conf: no such file or directory
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 (Moderate: OpenShift Container Platform 4.10.26 security update), 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/RHSA-2022:5875