-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17
-
Important
-
None
-
2
-
OSDOCS Sprint 261, OSDOCS Sprint 262
-
2
-
False
-
Description of problem:
"opm generate dockerfile" need to be updated, there is no "--binary-image".
Related epic: https://issues.redhat.com/browse/OPRUN-3346
xzha@xzha1-mac bin % opm generate dockerfile -h Generate a Dockerfile for a file-based catalog. This command creates a Dockerfile in the same directory as the <fbcRootDir> (named <fbcRootDir>.Dockerfile) that can be used to build the index. If a Dockerfile with the same name already exists, this command will fail. When specifying extra labels, note that if duplicate keys exist, only the last value of each duplicate key will be added to the generated Dockerfile. A separate builder and base image can be specified. The builder image may not be "scratch". Usage: opm generate dockerfile <fbcRootDir> [flags] Flags: -i, --base-image string Image base to use to build catalog. (default "quay.io/operator-framework/opm:latest") -b, --builder-image string Image to use as a build stage. (default "quay.io/operator-framework/opm:latest") -l, --extra-labels strings Extra labels to include in the generated Dockerfile. Labels should be of the form 'key=value'. -h, --help help for dockerfile Global Flags: --skip-tls-verify skip TLS certificate verification for container image registries while pulling bundles --use-http use plain HTTP for container image registries while pulling bundles
Version-Release number of selected component (if applicable):
release-4.17
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info: