You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nextflow run nf-core/mag -r 2.1.0 -profile test,singularity -c sge.conf
Error:
Error executing process > 'NFCORE_MAG:MAG:KRAKEN2_DB_PREPARATION'
Caused by:
Process `NFCORE_MAG:MAG:KRAKEN2_DB_PREPARATION` terminated with an error exit status (127)
Command executed:
mkdir db_tmp
tar -xf "minigut_kraken.tgz" -C db_tmp
mkdir database
mv `find db_tmp/ -name "*.k2d"` database/
Command exit status:
127
Command output:
(empty)
Command error:
env: singularity: No such file or directory
Work dir:
/isilon/lethbridge-rdc/users/ortegapoloro/mag_test/work/0e/c9cba40483c7e9397b2e23412fad15
Tip: view the complete command output by changing to the process work dir and entering the command `cat .command.out`
The issue you mentioned, nf-core/fetchngs#12, seems to me rather because of a wrong choice of container in the pipeline script. The fix was to use another container. However, it seems to me that your problem isn't related.
To me, your issue seems to be related to nf-core/eager#68, i.e. it might be a config problem.
But I admit that I am not an expert in that matter. I will use the pipeline in the next days, and if its a container problem I will run into it too (and fix it).
If you do want to test the potential config solution, please let me know in case that works, otherwise I think I have to refer you to the nf-core slack with more knowledgeable people for that problem.
Hi @d4straub ! Thank you so much for pointing me to the issue of the eager repo. Indeed this was a config problem, and I fixed this with the following in my config file. We don't have module in our cluster, and we are encouraged to use conda to activate the singularity env. This seems to work. Thank you for taking the time to look into this and replying to me!
Check Documentation
I have checked the following places for your error:
Description of the bug
Command:
nextflow run nf-core/mag -r 2.1.0 -profile test,singularity -c sge.conf
Error:
sge.conf:
Steps to reproduce
Steps to reproduce the behaviour:
Expected behaviour
Pipeline would launch jobs with the
sge
executor using Singularity images.Log files
Have you provided the following extra information/files:
.nextflow.log
fileSystem
Nextflow Installation
Container engine
Additional context
This issue might be similar to this other issue in
fetchngs
I do have a Singularity cache directory where those containers were already downloaded
The text was updated successfully, but these errors were encountered: