-
Notifications
You must be signed in to change notification settings - Fork 421
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
resolved path doesn't match with opened path singularity #804
Comments
Hi @jackmo375 which Nextflow version are your using? |
Im using nextflow v22. Im actually not using the sarek pipeline, just the container, with a custom pipeline. |
Thank you for your reply! I've been stuck on this for a while :) |
how do you specify the path to the container, or the singularity cache dir ? |
I specify the path to the sarek container image (.sif) in the config file, with the process scope. This image file is not in the same place as the singularity cache directory, and the cache directory path is also specified in the config file. I am running the pipeline on an HPC shared filesystem. |
Can you try supplying the singularity image with |
Hi @maxulysse OK I just tried with this option and had the same error: Command error: |
@pontus any idea on that one? |
What's the version of singularity here? |
I am running singularity 3.5.3 |
Then I'd recommend upgrading that for a start. |
Ah OK, for that I will have to contact the administrators of the HPC system I am using. This seems to be an issue with singularity rather than the sarek container? |
Yes, that's how it looks to me. |
As far as I understand this threat this issue is not sarek related. I am therefore closing it to keep track of bugs we need to fix. |
Description of the bug
I am encountering a bug previously described on the archived version of this pipeline here: SciLifeLab#780
basically the issue is that when I run a pipeline with the sarek container, I get the following:
Did anyone find a resolution to this issue? The thread ended when the pipeline was moved to nf core and I could not find the thread continued on this new repo.
Warm regards,
Jack
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: