Heads up:
We’re moving the GATK website, docs and forum to a new platform. Read the full story and breakdown of key changes on this blog.
Update: July 26, 2019
This section of the forum is now closed; we are working on a new support model for WDL that we will share here shortly. For Cromwell-specific issues, see the Cromwell docs and post questions on Github.

image ENTRYPOINT requirement

esalinasesalinas BroadMember, Broadie ✭✭✭

I have seen instances of where trying to run a command in an image
where the ENTRYPOINT is NOT /bin/bash leads to problems.

According to https://github.com/broadinstitute/cromwell#local-backend it says

The subprocess command that the local backend will launch is:

"/bin/bash" "-c" "cat script | <docker_run> /bin/bash <&0"

From my understanding this implies that running cromwell with a local backend
requires that the ENTRYPOINT of the image be /bin/bash. Is that correct??? If not, what are
the requirements for the ENTRYPOINT of the image???

Best Answer


  • esalinasesalinas BroadMember, Broadie ✭✭✭

    @KateN This would seem to be an important requirement (at least for now as you mention) because I have seen more than one docker's usage by cromwell have problems because of this issue. Because of that I think the requirement needs to be more prominently promulgated.

  • esalinasesalinas BroadMember, Broadie ✭✭✭

    I think that the CMD for the image also needs to be set as "/bin/bash".
    I think so because I was making a docker image and only set the ENTRYPOINT as /bin/bash but was still having problems
    and then set CMD as /bin/bash and that's what allowed successful execution on firecloud

Sign In or Register to comment.