Description of problem: The Makefile in branch release-4.10 has some targets with "podman" hard-coded and some targets with "docker" hard-coded. It means that you would always fail unless you have the two commands symlinked to each other. We need to parameterize the container command. Version-Release number of selected component (if applicable): release-4.10 How reproducible: 100% Steps to Reproduce: 1) Get the SRO repo: git clone https://github.com/openshift/special-resource-operator cd special-resource-operator git checkout release-4.10 2) Build and push: podman login -u <quay_user> quay.io IMAGE_TAG_BASE=quay.io/<quay_user>/special-resource-operator IMG=quay.io/<quay_user>/special-resource-operator make local-image-build local-image-push bundle bundle-build bundle-push 3) Create the namespace and run the bundle: apiVersion: v1 kind: Namespace metadata: name: openshift-special-resource-operator oc project openshift-special-resource-operator operator-sdk run bundle quay.io/<quay_user>/special-resource-operator-bundle:v0.0.1 Actual results: I only have podman, so I get: No rule to make target 'docker-push' Expected results: Use the right container command consistently Additional info: Proposed fix: https://github.com/openshift/special-resource-operator/pull/122
This bug is for the 4.10 branch only, although it is opened on 4.11. Don't merge this into 4.11.
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.10.8 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:1162