We've moved!
For WDL questions, see the WDL specification and WDL docs.
For Cromwell questions, see the Cromwell docs and please post any issues on Github.


KateNKateN Cambridge, MAMember, Broadie, Moderator admin
edited October 2016 in Components

The runtime component is an optional property of a task. It can be used to specify environment parameters through key/value pairs. These can be set arbitrarily, but the backend is responsible for interpreting these values. Cromwell currently supports three backends, local, JES, and SGE, which interpret the following runtime attributes:

Runtime Attribute LOCAL JES SGE
continueOnReturnCode x x x
cpu x x
disks x
zones x
docker x x x
failOnStderr x x x
memory x x
preemptible x
bootDiskSizeGb x

Note that there are two special reserved keys:

  • docker
    Docker image on which to run the task command. Although not required for general use, it is very useful in contexts such as cloud execution services. For example, you will be required to use Docker images if you plan to run Cromwell using a Java Execution Service. For information on how to generate a Docker image, please read this guide.

  • memory
    Memory requirements for the task. This should be an integer value with suffixes like B, KB, MB, or binary suffixes KiB, MiB and so on. Note that Cromwell does not honor this parameter if running on a local machine (e.g. a laptop).

Usage example

runtime {
    docker: "organization/myImage"

Further details in the WDL spec

Post edited by KateN on
Sign In or Register to comment.