Scientific workflow engine designed for simplicity & scalability. Trivially transition between one off use cases to massive scale production environments
Im testing moving LSAPI runs to Batch with v86, and I keep getting the following error:
textPayload: "docker: invalid spec: /mnt/disks/cromwell_root:/mnt/disks/cromwell_root:: empty section between colons."
for this command:
Executing runnable container:{image_uri:"gcr.io/google.com/cloudsdktool/cloud-sdk:434.0.0-alpine" commands:"-c" commands:"printf '%s %s\n' \"$(date -u '+%Y/%m/%d %H:%M:%S')\" Starting\ container\ setup." entrypoint:"/bin/sh" volumes:"/mnt/disks/cromwell_root:/mnt/disks/cromwell_root:"} timeout:{seconds:300} labels:{key:"logging" value:"ContainerSetup"} for Task task/job-49cc8a88-722b-43067ba4-ab34-48bc00-group0-0/0/0 in TaskGroup group0 of Job job-49cc8a88-722b-43067ba4-ab34-48bc00.
The docker volumes are defined as:
volumes:"/mnt/disks/cromwell_root:/mnt/disks/cromwell_root:"}
Shouldn't there be a rw permissions entry after the last colon? As far as I know, there is no way for users to modify the docker launch config to fix this. Is there something I have malformed or missing in my conf file?
Im testing moving LSAPI runs to Batch with v86, and I keep getting the following error:
textPayload: "docker: invalid spec: /mnt/disks/cromwell_root:/mnt/disks/cromwell_root:: empty section between colons."
for this command: Executing runnable container:{image_uri:"gcr.io/google.com/cloudsdktool/cloud-sdk:434.0.0-alpine" commands:"-c" commands:"printf '%s %s\n' \"$(date -u '+%Y/%m/%d %H:%M:%S')\" Starting\ container\ setup." entrypoint:"/bin/sh" volumes:"/mnt/disks/cromwell_root:/mnt/disks/cromwell_root:"} timeout:{seconds:300} labels:{key:"logging" value:"ContainerSetup"} for Task task/job-49cc8a88-722b-43067ba4-ab34-48bc00-group0-0/0/0 in TaskGroup group0 of Job job-49cc8a88-722b-43067ba4-ab34-48bc00.
The docker volumes are defined as: volumes:"/mnt/disks/cromwell_root:/mnt/disks/cromwell_root:"}
Shouldn't there be a rw permissions entry after the last colon? As far as I know, there is no way for users to modify the docker launch config to fix this. Is there something I have malformed or missing in my conf file?