Build CVO from UBI8 instead of obsolete origin-v4.0:base
#872
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think the bare
Dockerfileonly supports developer usecases (#871), we build the product withDockerfile.rhel. We should use the modern base images even for this scenario.I have considered using upstream registry.access.redhat.com pullspec (https://catalog.redhat.com/software/containers/ubi8/5c647760bed8bd28d0e38f9f?container-tabs=gti) which should also allow unauthenticated access, but we use registry.ci.openshift.org in the first
FROManyway, and UBI images are periodically mirrored to registry.ci.openshift.org so we get the same stuff.