You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix bundle build command with Docker and update documentation
The bundle build command using Docker fails in some cases due
to Docker can't access some files which in turn due to issue
with generated Docker command doesn't account for manifests
directory. The `ADD` command in Dockerfile is now changed to
`COPY` given we don't use any features from ADD.
Update documentation + unit test cases for those above changes.
Signed-off-by: Vu Dinh <[email protected]>
Copy file name to clipboardexpand all lines: docs/design/operator-bundle.md
+6-1
Original file line number
Diff line number
Diff line change
@@ -159,6 +159,12 @@ The `--package` or `-p` is the name of package fo the operator such as `etcd` wh
159
159
160
160
All information in `annotations.yaml` is also existed in `LABEL` section of `Dockerfile`.
161
161
162
+
The `Dockerfile` can used to manually build bundle image using container image tools such as Docker, Podman or Buildah. For example, the Docker build command would be:
Operator bundle image can be built from provided operator manifests using `build` command (see *Notes* below). The overall `bundle build` command usage is:
@@ -196,4 +202,3 @@ The `--package` or `-p` is the name of package fo the operator such as `etcd` wh
196
202
*Notes:*
197
203
* If there is `Dockerfile` existing in the directory, it will be overwritten.
198
204
* If there is an existing `annotations.yaml`in`/metadata` directory, the cli will attempt to validate it and returns any found errors. If the ``annotations.yaml`` is valid, it will be used as a part of build process. The optional boolean `--overwrite/-o` flag can be enabled (false by default) to allow cli to overwrite the `annotations.yaml`if existed.
199
-
* The directory where the operator manifests are located must be inside the context of the build which in this case is inside the directory where you run the command.
0 commit comments