Open tschoonj opened 2 years ago
As a workaround, it might work if you use relative paths in the cwl.output.json
.
For the general case, cwltool
would probably need to apply reverse path mapping to cwl.output.json
to get the paths outside the container.
Hi all,
I am experimenting with
cwl.output.json
to get the results back from a CommandLineTool that executes in a Docker environment. This works fine, but there appears to be a problem when re-running the same workflow:cwltool
correctly recognizes that the cache can be used, but it chokes on the filepath that was saved into thecwl.output.json
file which contains a path to a random generated folder that was used during the first run.Expected Behavior
Caching should work fine, as expected
Actual Behavior
When retrying, I get the following error:
The initial run produced:
Workflow Code
CommandLineTool
arv-get.cwl
:The
arv-get-cwl
script within the container extracts the input fromcwl.inputs.json
and passes it to thearv-get
command, after which thecwl.output.json
file is produced with the filename:Workflow spike.cwl:
Your Environment
cwltool --version
CC @jrandall