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

Singularity container execution of pangolin crashes with recent nextflow versions #272

Open
Krannich479 opened this issue May 27, 2024 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@Krannich479
Copy link

Hi,
I noticed that poreCov crashes when running pangolin via singularity and a reasonably modern nextflow version. It seems that recent updates in the path mounting defaults of nextflow broke the default behavior of poreCov test profiles when using Singularity. More precise, when using the command

nextflow run poreCov.nf -profile test_fastq,slurm,singularity --update

with nextflow 23.10.1 and poreCov 1.9.4 I end up with

[f3/91e3e5] NOTE: Process `determine_lineage_wf:pangolin (1)` terminated with an error exit status (1) -- Execution is retried (1)
ERROR ~ Error executing process > 'determine_lineage_wf:pangolin (1)'

Caused by:
  Process `determine_lineage_wf:pangolin (1)` terminated with an error exit status (1)

Command executed:

  pangolin --skip-scorpio -t 4 SARSCoV2.consensus.fasta

  mv lineage_report.csv lineage_report_SARSCoV2.csv

  find . -name "*.csv" -size  0 -print -delete

Command exit status:
  1

Command output:
  ****
  Pangolin skipping scorpio steps.
  ****
  ****
  Pangolin running in usher mode.
  ****
  Maximum ambiguity allowed is 0.3.
  ****
  Query file:ameSARSCoV2.consensus.fasta
  ****
  Data files found:
  usher_pb:     /opt/conda/lib/python3.7/site-packages/pangolin_data/data/lineageTree.pb
  ****

Command error:
  Traceback (most recent call last):
    File "/opt/conda/lib/python3.7/site-packages/snakemake/__init__.py", line 642, in snakemake
      latency_wait=latency_wait,
    File "/opt/conda/lib/python3.7/site-packages/snakemake/workflow.py", line 242, in __init__
      self.sourcecache = SourceCache()
    File "/opt/conda/lib/python3.7/site-packages/snakemake/sourcecache.py", line 358, in __init__
      os.makedirs(self.cache, exist_ok=True)
    File "/opt/conda/lib/python3.7/os.py", line 213, in makedirs
      makedirs(head, exist_ok=exist_ok)
    File "/opt/conda/lib/python3.7/os.py", line 213, in makedirs
      makedirs(head, exist_ok=exist_ok)
    File "/opt/conda/lib/python3.7/os.py", line 213, in makedirs
      makedirs(head, exist_ok=exist_ok)
    [Previous line repeated 1 more time]
    File "/opt/conda/lib/python3.7/os.py", line 223, in makedirs
      mkdir(name, mode)
  OSError: [Errno 30] Read-only file system: '/home/<myHPCusername>'

Additional Info:

The same command works fine and tests finish if I use nextflow 21.04.0. @MarieLataretu found these update notes that seem on point for this issue:
https://github.com/nextflow-io/nextflow/blob/d8f8bf56cfe79dc05db7c149dafa0174717ae7f4/docs/container.md?plain=1#L580
https://github.com/nextflow-io/nextflow/blob/d8f8bf56cfe79dc05db7c149dafa0174717ae7f4/docs/container.md?plain=1#L584

@Krannich479 Krannich479 added the bug Something isn't working label May 27, 2024
@replikation
Copy link
Owner

ah "OSError: [Errno 30] Read-only file system: '/home/'"

is a singularity error @hoelzer can you tune in you had this OS errors before

@replikation
Copy link
Owner

maybe the answer with the --writable helps for singularity:

https://stackoverflow.com/questions/65599721/unable-to-build-writable-singularity-container

@MarieLataretu
Copy link
Collaborator

I'm wondering why this error occurs (only?) with the pangolin container. Apparently, it needs to have access to home?

@Krannich479, did you also try setting NXF_SINGULARITY_HOME_MOUNT to true with a recent Nexflow version?

@replikation
Copy link
Owner

based on the error pangolin wants to write something in its own container home directory. and singularitys home is not writable. as far as i understand (?) but this is something that the user controls with its own singularity system. it could be that however, we need to add as a flag to the config or so

@hoelzer
Copy link
Collaborator

hoelzer commented May 27, 2024

Uff... yes that is annoying and someone else here had this problem recently - for me it still worked bc my nf version is 22.x.x or so.

I am not sure what is happening inside the pangolin container but yeah, the problem is that pangolin wants to write something in /home which is fine with a encapsulated Docker container but fails with Singularity. Because here the process actually tries to write in the HPC system path.

@Krannich479
Copy link
Author

@Krannich479, did you also try setting NXF_SINGULARITY_HOME_MOUNT to true with a recent Nexflow version?

Tried this, didn't work for me :/

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