Closed ryan-salo closed 2 years ago
Hi @ryan-salo!
Dsub currently sets the ENTRYPOINT of the user-command image to be /usr/bin/env
, and the CMD to be -c bash {USER_SCRIPT}
. This is done because there is some setup/cleanup scripting done that requires Bash (which is why your --image
must include the Bash shell interpreter).
You're only able to change things after dsub calls /usr/bin/env -c bash
through your --script
or --command
inputs.
If this doesn't work for you please send us further details and we can help out more.
@wnojopra , thanks for the feedback! This makes sense given the setup/cleaning that happens, and I can work with that. Just wanted to double check if there was a way to use an existing ENTRYPOINT.
Is there way to tell dsub to use the existing entrypoint of an image and pass it command args? Or is this a limitation of lifesciences pipelines?