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

resolved path doesn't match with opened path singularity #804

Closed
jackmo375 opened this issue Oct 21, 2022 · 14 comments
Closed

resolved path doesn't match with opened path singularity #804

jackmo375 opened this issue Oct 21, 2022 · 14 comments
Labels
bug Something isn't working

Comments

@jackmo375
Copy link

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:

Error executing process > 'trimSampleReads (18)'

Caused by:
  Process `trimSampleReads (18)` terminated with an error exit status (255)

Command executed [/mnt/lustre/users/jmorrice/projects/fifty-genomes/templates/pre-processing/trim-sample-reads.sh]:

  #!/bin/bash
  
  trim_galore     --basename SCD-369_trimmed     --paired     --fastqc     --gzip     HCFVTCCXX-7_S0_L007_R1_001.fastq.gz HCFVTCCXX-7_S0_L007_R2_001.fastq.gz

Command exit status:
  255

Command output:
  (empty)

Command error:
  FATAL:   resolved path /mnt/lustre/users/jmorrice/projects/fifty-genomes/software/sarek_latest.sif doesn't match with opened path /mnt/lustre/users/jmorrice/projects/fifty-genomes/software/sarek_latest.sif (deleted)

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

@jackmo375 jackmo375 added the bug Something isn't working label Oct 21, 2022
@maxulysse
Copy link
Member

Hi @jackmo375 which Nextflow version are your using?
And which Sarek version?

@jackmo375
Copy link
Author

Im using nextflow v22. Im actually not using the sarek pipeline, just the container, with a custom pipeline.

@jackmo375
Copy link
Author

Thank you for your reply! I've been stuck on this for a while :)

@maxulysse
Copy link
Member

how do you specify the path to the container, or the singularity cache dir ?
In either command line, config file, or profile, env variable...

@jackmo375
Copy link
Author

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.

@maxulysse
Copy link
Member

Can you try supplying the singularity image with -with-singularity /mnt/lustre/users/jmorrice/projects/fifty-genomes/software/sarek_latest.sif?

@jackmo375
Copy link
Author

Hi @maxulysse OK I just tried with this option and had the same error:

Command error:
FATAL: resolved path /mnt/lustre/users/jmorrice/projects/fifty-genomes/software/sarek_latest.sif doesn't match with opened path /mnt/lustre/users/jmorrice/projects/fifty-genomes/software/sarek_latest.sif (deleted)

@maxulysse
Copy link
Member

@pontus any idea on that one?

@pontus
Copy link

pontus commented Oct 24, 2022

apptainer/singularity#3249?

What's the version of singularity here?

@jackmo375
Copy link
Author

I am running singularity 3.5.3

@pontus
Copy link

pontus commented Oct 24, 2022

Then I'd recommend upgrading that for a start.

@jackmo375
Copy link
Author

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?

@pontus
Copy link

pontus commented Oct 24, 2022

Yes, that's how it looks to me.

@FriederikeHanssen
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants