When building without a Containerfile, and using UBI8 (ubi8/ubi-minimal:8.10 or any other for that matter) - and not specifying entrypoint, buildah config ends up writing this:
Note, that the UBI image in question has no ENTRYPOINT, but does have a CMD as per its Dockerfile. I saw in an older buildah issue, that in the presence of an ENTRYPOINT, CMD should be ignored, but this doesn't seem to be the case, as when I do specify an entrypoint to the action, we end up with both:
"Cmd": [
"/bin/bash"
],
"Entrypoint": [
"bash"
],
I've tried this with/without OCI - no difference.
Steps to reproduce, workflow links, screenshots
This is all with buildah version 1.33.7 (image-spec 1.1.0-rc.5, runtime-spec 1.1.0)
Version
redhat-actions/push-to-registry@v2
Describe the bug
When building without a Containerfile, and using UBI8 (
ubi8/ubi-minimal:8.10
or any other for that matter) - and not specifyingentrypoint
,buildah config
ends up writing this:.. and the resulting image's manifest:
This bracket is being returned from this line.
Note, that the UBI image in question has no
ENTRYPOINT
, but does have aCMD
as per its Dockerfile. I saw in an older buildah issue, that in the presence of anENTRYPOINT
,CMD
should be ignored, but this doesn't seem to be the case, as when I do specify anentrypoint
to the action, we end up with both:I've tried this with/without OCI - no difference.
Steps to reproduce, workflow links, screenshots
This is all with
buildah version 1.33.7 (image-spec 1.1.0-rc.5, runtime-spec 1.1.0)
The step and its enumerated inputs:
Cheers!