proposal: use args not command for kubernetes
See original GitHub issueHi,
thanks for this great project 😃
I noticed that in a few places (helm chart, dagster-celery-k8s) pipeline pods are creating setting the command
to dagster
.
There is a different meaning between command
in k8s and in docker, because in kubernetes what is specified in command
overrides the image entrypoint (see: kubernetes docs). This might be a problem for docker images where the entrypoint is set (e.g. to provide a conda environment).
Would it be possible to not set command and use args instead so that the entrypoint is preserved? In alternative, is it possible to let the user specify the command and args?
This is just a proposal, but if you are happy with it I can try opening a PR.
Thanks again 🙂
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Cannot use args to pass arguments to a pod - Stack Overflow
I am unable to pass arguments to a container entry point. The error I am getting is: ... So Kubernetes just had the...
Read more >Using Commands and Arguments in a Kubernetes Pod
In the context of this topic, we will be dealing with ways to create and define commands and arguments for a container running...
Read more >how to pass kubernetes pods arguments like Docker ...
Kubernetes POD arguments will not pass from singlePod.yaml file: ... I want the arguments to be accepted just like the Docker command line....
Read more >Command and Args fields - Discuss Kubernetes
If I want to start myBinary with just one line (putting all the parameters there) I need to start it using shell? I...
Read more >Kubernetes | Jenkins plugin
Then, use it as the jnlp container for the pod template as usual. No command or args need to be specified. Notes: Support...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m running into this with user code deployments too, specifically using a micromamba base image with conda environments.
The dagster kubernetes chart still uses the “command” in the user template deployment. Is this on purpose or would the same logic apply there as well?
I’m running in to the same problem there trying to use dagster that’s installed in a conda environment
https://github.com/dagster-io/dagster/blob/a790cd3736eecccea0e63777e0853213b2eba507/helm/dagster/charts/dagster-user-deployments/templates/deployment-user.yaml#L44