These are chat archives for nextflow-io/nextflow

17th
Aug 2016
Mike Smoot
@mes5k
Aug 17 2016 19:44
@pditommaso Hi Paolo, with the fat docker container strategy we were discussing earlier, does the entire workflow run within one container or does each process create its own container?
Paolo Di Tommaso
@pditommaso
Aug 17 2016 19:46
one image, but many containers ..
Mike Smoot
@mes5k
Aug 17 2016 19:47
Apart from running nextflow from within docker do you know of a way to get just one container?
Paolo Di Tommaso
@pditommaso
Aug 17 2016 19:48
um, no
maybe using docker exec but it looks a mess
Mike Smoot
@mes5k
Aug 17 2016 19:51
Maybe just running nextflow within a container wouldn't be so horrible. Unfortunately, having many containers doesn't solve the problem of errors when spawning docker containers concurrently or a separate problem we've been having which are slow startup times for large images.
Paolo Di Tommaso
@pditommaso
Aug 17 2016 19:52
have u tried the overlay storage driver ?
I can share an EC2 instance with that if u need
Mike Smoot
@mes5k
Aug 17 2016 19:53
Not yet - that requires stopping large jobs in progress, so it takes some planning.
Paolo Di Tommaso
@pditommaso
Aug 17 2016 19:53
I see
Mike Smoot
@mes5k
Aug 17 2016 19:53
I think I can get my hands on an EC2 instance of our own. I think our lawyers might get upset if I put our data somewhere else! :)
Paolo Di Tommaso
@pditommaso
Aug 17 2016 19:54
anyway in your case running just running docker run <image> nextflow ... etc it's the best solution
Mike Smoot
@mes5k
Aug 17 2016 19:54
I think for now you're probably right.