Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose XIMMER_REF in config.groovy rather than a env variable for docker run #25

Open
sclan opened this issue Jul 11, 2019 · 0 comments

Comments

@sclan
Copy link

sclan commented Jul 11, 2019

This is a suggestion.

We have a docker platform that users can use the following input to run tools via docker image:
input data files: (e.g,: *.bam, ref.fa, taget_region.bed)
cmd: (e.g. ximmer -c config.groovy -o ./out -v)
image: (e.g. ssadedin/ximmer)

Then the platform will run the following command:
docker run -w /tmp -v ~/./out:/tmp ssadedin/ximmer ximmer -c config.groovy -o -v

The "docker run -w /tmp -v ~/./out:/tmp" is hard coded on our platform (and any output will be copied from /tmp to the final storage that users can access by the platform's post-processing mechanism). The rest of the command is provided by the user and the input data are copied to the home directory on the execution server.

Would be nice to allow users to specify the reference fasta file via the config file instead of passing it into the docker environment via "-e".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant