-
Notifications
You must be signed in to change notification settings - Fork 660
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
/bin/bash: .command.sh: No such file or directory #1732
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is this issue solved? I used most updated nextflow (version 21.10.6.5660), but still have the same error. my singularity version is 3.7.0 |
I finally found a solution for our cluster. The config file (nextflow.config) should look like this: process.container = 'PATH to your container' the two links can be identified with pwd and readlink -f . Hope it helps |
When using a singularity container, I have to specify a bind path in the nextflow.config like so:
where $PWD is the folder with my main.nf file, nextflow.config file, and work folder. |
Bug report
When I activate the singularity container, nextflow crash and tells me that .command.sh don't exist
This appears after an update to singularity 3.6.0
Expected behavior and actual behavior
nextflow ORPER.nf --refgroup=Nostocales --outgroup=Gloeobacterales --ribodb=/data1/ORPER/ribo/ --companion=ORPER/ORPER-companion.py --SSU=Nostocales-silva.fasta --cdhit=no
This commands and pipeline work well. but is I activate the container with :
process.container = '/data1/ORPER/ORPER.sif'
singularity.enabled = true
it crash
Steps to reproduce the problem
but when I activate the container with :
process.container = '/data1/ORPER/ORPER.sif'
singularity.enabled = true
it crash
Program output
ommand exit status:
1
Command output:
(empty)
Command error:
/bin/bash: line 0: cd: /data1/ORPER/work/17/5e87858643dcc828837406eecff1b8: No such file or directory
/bin/bash: .command.sh: No such file or directory
Work dir:
/data1/ORPER/work/17/5e87858643dcc828837406eecff1b8
Environment
The text was updated successfully, but these errors were encountered: