GitHub Community
Custom entrypoint for container jobs #26465
-
|
Is there a way I can define the entrypoint and startup command used by a container job? It From lookingat the “Initialize Containers” step shows the container always getting created with |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi @chuckatkins , Using custom entrypoint and startup command for a container job is not supported. The ** --entrypoint “tail” <image name> “-f” “/dev/null”** in “Initialize Containers” step is to keep the container running. If you want to run some startup command, I would recommend you adding a run script step as the first step of the job. |
Beta Was this translation helpful? Give feedback.
Hi @chuckatkins ,
Using custom entrypoint and startup command for a container job is not supported.
The ** --entrypoint “tail” <image name> “-f” “/dev/null”** in “Initialize Containers” step is to keep the container running.
If you want to run some startup command, I would recommend you adding a run script step as the first step of the job.