Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In container support for specifying command #129

Closed
surajssd opened this issue May 18, 2017 · 1 comment
Closed

In container support for specifying command #129

surajssd opened this issue May 18, 2017 · 1 comment

Comments

@surajssd
Copy link
Contributor

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/

$ 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
@surajssd
Copy link
Contributor Author

this is dup of #91 closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant