Right now with OpenCompose there is no way we can define a command that overrides the docker image's ENTRYPOINT. If someone wants this to happen they have to bake it inside the container image. This would be a great thing to have to override what runs inside container image on k8s.
$ oc explain deployment.spec.template.spec.containers.command
FIELD: command <[]string>
DESCRIPTION:
Entrypoint array. Not executed within a shell. The docker image's
ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME)
are expanded using the container's environment. If a variable cannot be
resolved, the reference in the input string will be unchanged. The
$(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME).
Escaped references will never be expanded, regardless of whether the
variable exists or not. Cannot be updated. More info:
http://kubernetes.io/docs/user-guide/containers#containers-and-commands
Right now with OpenCompose there is no way we can define a command that overrides the docker image's
ENTRYPOINT
. If someone wants this to happen they have to bake it inside the container image. This would be a great thing to have to override what runs inside container image on k8s.Read about it at: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/