Bug 2107690

Summary:	Driver Container builds fail with "error determining starting point for build: no FROM statement found"
Product:	OpenShift Container Platform	Reporter:	Enrique Belarte <ebelarte>
Component:	Special Resource Operator	Assignee:	Brett Thurber <bthurber>
Status:	CLOSED ERRATA	QA Contact:	Udi Kalifon <ukalifon>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.10
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 11:21:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2107678

Description Enrique Belarte 2022-07-15 16:18:10 UTC

This bug was initially created as a copy of Bug #2107678

I am copying this bug because: 



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

Comment 2 errata-xmlrpc 2022-08-10 11:21:24 UTC

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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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:5069