Closed Jane-Gibson closed 1 month ago
Hi @Jane-Gibson, rather fortuitously another user reported a similar issue yesterday: https://github.com/epi2me-labs/wf-human-variation/issues/161. It appeared to be related to how data partitions are mounted on their cluster. I would have a chat with your HPC administrator about this error in the first instance as they should hopefully be able to advise on the specifics of your HPC better than we can.
ok, thanks. I will ask them and point them to the other issue.
Operating System
Other Linux (please specify below)
Other Linux
redhat
Workflow Version
v.1.1.0
Workflow Execution
Command line
EPI2ME Version
No response
CLI command run
run test data
${nextflow_exe_path} run epi2me-labs/wf-somatic-variation \ --bam_normal wf-somatic-variation-demo/demo_normal.bam \ --bam_tumor wf-somatic-variation-demo/demo_tumor.bam \ --ref wf-somatic-variation-demo/GCA_000001405.15_GRCh38_no_alt_analysis_set_chr20.fna \ --sv \ --snv \ --mod \ --sample_name SAMPLE \ --normal_min_coverage 0 \ --tumor_min_coverage 0 \ -profile apptainer \
Workflow Execution - CLI Execution Profile
singularity
What happened?
I'm running the somatic nextflow workflow via apptainer (singularity) on our HPC. It is failing at bam_ingress_normal:minimap2_ubam due to Relocation not allowed with starter-suid.
Is there a way to change our apptainer set up to allow this? or some option I should enable? thanks.
Relevant log output
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
no
Other demo data information
No response