-
Notifications
You must be signed in to change notification settings - Fork 44
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
using my own Docker from Gitlab #225
Comments
Hello! Indeed the easiest way to alter the containers used for a given process is to edit the For example, to alter a container for the spades container i would do:
When I open up the
More information on this is available in FlowCraft's docs here. ;) I hope this is helpful! Inês |
thanks a lot!! I will try directly :-) |
I tried....and get an error: There are fastq-files! see below... ..> ll data/ |
Hello. So this is an error when you run your nextflow pipeline, correct? Could you paste the nextflow command you are using? And the top of the params.config file? Also, there's an issue with the latest nextflow version that breaks flowcraft generated pipelines, so you need to check what version of nextflow you are using :/ (see #217 for more info). |
I see...I used the command now without indicating --fastq: I already downgraded nextflow to 18.10.1.5003 BTW - where is this integrity_coverage thing always coming from? |
the |
I have actually a trimmomatic issue... I made a docker with trimmomatic v.39. ...looks like the nextflow pipeline is referring to trimmomatic v. 0.36, which is the one you have in your docker hub. Also in the command.sh I see: TRIM_PATH = "/NGStools/Trimmomatic-0.36/trimmomatic.jar" what I see in the nextflow.log file is the following: 2019-10-02 10:15:40,995 - DEBUG - Finished template at 2019-10-02 10:15:40 My container.config file looks good, only listing the containers I referenced from my inhouse registry. Thus, where does this link to "your" trimmomatic docker container comes from? |
This discussion is moving a little bit away from the original issue, so I suggest maybe using gitter? https://gitter.im/flowcraft-community/community?source=orgpage |
Looking at the trimmomatic component better, in addition to the adapters, it's had another limitation that makes it only compatible with the flowcraft trimmomatic container. This could definitely be improved. Could you please e-mail me at cimendes@medicina.ulisboa.pt so that I could discuss a few technicalities with you so that can correct this behavior? Thanks! |
Hi there,
I was wondering how I can tell flowcraft to use my own docker, which are placed in an inhouse gitlab repository. I know, it is better to use those from flowcraft, but for some things I might need to use very specific versions of tools or maybe even docker container based on self made scripts. What I managed already is to simple exchange the "address" of the container in the container.config generated by flowcraft build.
However, as far as I understand - by default the pipeline is built with those containers available in the flowcraft docker hub repository. Thus I am wondering, if I can at all use docker container which are not listed in the flowcraft docker hub but only in our gitlab repository and how I tell flowcraft to use them. I hope I did not miss that point in your docs...
Greets
The text was updated successfully, but these errors were encountered: