Ivo Jimenez

> My hunch is that it is more common to prepare everything for an experiment on the login node, while the actual execution happens on the computing nodes. For example,...

sorry, I didn't explain well. What I had in mind was running the entire workflow first on the frontend node once, so it builds containers, but in single-node mode (i.e....

yeah, that sounds good. I'd go further and say to not implement ii) until users request it

@wtraylor any feedback on the above would be greatly appreciated 🙏

thanks a lot for the feedback @wtraylor! I agree 100% on the 80-20 rule. I should have specified that this `image` attribute would not be replacing the current `uses` one...

high-level outline of how this would be implemented: 1. add changes to the [YAML spec](https://github.com/getpopper/popper/blob/b672201/src/popper/parser.py#L17) so it supports the syntax specified in the OP. 2. write new tests for this...

@jaimistry12 sounds good. Let us know if y'all have any questions, we'll be happy to help.

thanks a lot for the prompt reply! i'm not too familiar with the ci workflows of this repo. I see that the 1.22.2 image has been getting updated with merges...

thanks @aojea! we've tested with 1.22.2 and problem persists. as a workaround, we're using an image obtained from this commit on our fork https://github.com/vectorizedio/kind/commit/fc74b98229783c265ca4ac8043b395364d72f4a2

Hi @mr-c, thanks a lot for reaching out. We learned about CWL thanks to a reference from the Genomics folks here at UCSC (devs of Toil). I investigated a bit...