Custom entrypoint for container jobs

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 --entrypoint "tail", evn if I pass a differnt entrypoint in the create actions then the “tail” entrypoint is still added after.

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.