Closed ChristopherRichie closed 1 year ago
Hi @ChristopherRichie,
Looking at your logs it seems to me that you are automatically loading additional Nextflow config files (presumably in you home directory?).
The error here is that you don't have docker available on your cluster, which is assumed by our default Nextflow profile. You will need to provide the name of your institution specific Nextflow profile (judging by some of the other logging it looks like your additional config is an nf-core institutional profile).
All the workflow code is available as container images on Dockerhub that should be useable from your HPCs preferred tool for running containers.
Hi Chris, thanks for the fast reply.
The README indicates that either Docker or Singularity is sufficient to run the workflow.
NIH BIOWULF HPC will only allow Singularity. (Docker is not available.)
Can you clarify if this workflow will work with singularity alone?
If so, can you suggest how I might modify my nextflow.config (s) to work without Docker?
Thanks
From: Chris Wright @.> Sent: Wednesday, April 19, 2023 12:59 PM To: epi2me-labs/wf-clone-validation @*.**@*.> Cc: Richie, Christopher (NIH/NIDA) [E] @.>; Mention @.***> Subject: [EXTERNAL] Re: [epi2me-labs/wf-clone-validation] [Bug]: test run fails (again) (Issue #18)
Hi @ChristopherRichiehttps://github.com/ChristopherRichie,
Looking at your logs it seems to me that you are automatically loading additional Nextflow config files (presumably in you home directory?).
The error here is that you don't have docker available on your cluster, which is assumed by our default Nextflow profile. You will need to provide the name of your institution specific Nextflow profile (judging by some of the other logging it looks like your additional config is an nf-core institutional profile).
All the workflow code is available as container images on Dockerhub that should be useable from your HPCs preferred tool for running containers.
- Reply to this email directly, view it on GitHubhttps://github.com/epi2me-labs/wf-clone-validation/issues/18#issuecomment-1515069984, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AR4COQ47XBPCKBTDFTXG2QDXCAKTTANCNFSM6AAAAAAXEKZI2U. You are receiving this because you were mentioned.Message ID: @.**@.>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe.
The workflow can run with singularity. How to do that depends intimately on your cluster setup. You should talk to your cluster administrators for advice.
Following the breadcrumbs from your log messages led me to https://hpc.nih.gov/apps/nextflow.html which appears to contains useful information. Your institutional nextflow config appears to provide a biowolf profile that you likely need to set. Though I can't really comment and again you should talk to your cluster admins.
Thanks Chris
thanks for confirming that the wf can work with just singularity. I will follow up with my cluster admins
Thanks
From: Chris Wright @.> Sent: Wednesday, April 19, 2023 4:08 PM To: epi2me-labs/wf-clone-validation @.> Cc: Richie, Christopher (NIH/NIDA) [E] @.>; Mention @.> Subject: [EXTERNAL] Re: [epi2me-labs/wf-clone-validation] [Bug]: test run fails (again) (Issue #18)
The workflow can run with singularity. How to do that depends intimately on your cluster setup. You should talk to your cluster administrators for advice.
Following the breadcrumbs from your log messages led me to https://hpc.nih.gov/apps/nextflow.html which appears to contains useful information. Your institutional nextflow config appears to provide a biowolf profile that you likely need to set. Though I can't really comment and again you should talk to your cluster admins.
- Reply to this email directly, view it on GitHubhttps://github.com/epi2me-labs/wf-clone-validation/issues/18#issuecomment-1515313486, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AR4COQ6U4EQPQQ2ISNSD543XCBAZTANCNFSM6AAAAAAXEKZI2U. You are receiving this because you were mentioned.Message ID: @.**@.>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe.
Closing through lack of response from original poster
What happened?
I am running on the NIH HPC, with nextflow singularity CUDA When I run the test command, i get this error:
Operating System
Windows 10
Workflow Execution
EPI2ME Labs desktop application
Workflow Execution - EPI2ME Labs Versions
No response
Workflow Execution - CLI Execution Profile
None
Workflow Version
N E X T F L O W ~ version 22.10.4 Launching
https://github.com/epi2me-labs/wf-clone-validation
[infallible_venter] DSL2 - revision: 8f800c1aa5 [master]Relevant log output