-
Notifications
You must be signed in to change notification settings - Fork 41
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
nf-core failure to attain singularity containers #168
Comments
Hi @bcardus, our Docker images are not hosted on quay.io. I have not used the If you want to simply pull our images with Singularity, you should be able to accomplish this by removing the reference to quay.io:
Note the command will first pull the Docker image in order to build the Singularity image, as we do not host a registry of native Singularity images. |
Hi Sam,
Thank you for the pointers and apologies if I submitted this to the wrong github page.
The modifier -l docker.io solved the registry issue noted above.
For anyone who finds this thread in the future, I still got different errors after that (creating the SIF file failed for unclear reasons). However, I was able to pull the images from Singularity one by one as you suggested. I had some issues with running out of disc space as I could not figure out how to set the cache to the right folder, and in the end I used the --disable-cache option. This all worked in the end, and I managed to run the workflow.
Thank you again!
Best wishes,
Bea
From: Sam Nicholls ***@***.***>
Sent: Wednesday, April 3, 2024 10:22 PM
To: epi2me-labs/wf-human-variation ***@***.***>
Cc: Cardus, Beatrix (RTH) OUH ***@***.***>; Mention ***@***.***>
Subject: Re: [epi2me-labs/wf-human-variation] nf-core failure to attain singularity containers (Issue #168)
Hi @bcardus<https://github.com/bcardus>, our Docker images are not hosted on quay.io. I have not used the nf-core download command but from a cursory glance at the docs<https://nf-co.re/tools#downloading-pipelines-for-offline-use> it looks like you might need to supply -l docker.io to override the registry. For any further support on the nf-core tools I would ask the nf-core community<https://nf-co.re/join>.
If you want to simply pull our images with Singularity, you should be able to accomplish this by removing the reference to quay.io:
$ singularity pull --name ontresearch-modkit-shaeedb131a939d3eea2f9bd4dbecec805c0fa20bdb.img docker://ontresearch/modkit:shaeedb131a939d3eea2f9bd4dbecec805c0fa20bdb
Note the command will first pull the Docker image in order to build the Singularity image, as we do not host a registry of native Singularity images.
-
Reply to this email directly, view it on GitHub<#168 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A4KFTDOXHQ4SZ66MCKNVYMLY3RXGPAVCNFSM6AAAAABFWB2GDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGYYTMNRTGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Operating System
CentOS 7
Other Linux
CentOS Linux 7 (Core)
Workflow Version
v2.1.0
Workflow Execution
Command line (Cluster)
Other workflow execution
No response
EPI2ME Version
No response
CLI command run
[hzs682@rescomp2 hzs682]$ nf-core download epi2me-labs/wf-human-variation --force
? Select release / branch: v2.1.0 [release]
? Include the nf-core's default institutional configuration files into the download? Yes
In addition to the pipeline code, this tool can download software containers.
? Download software container images: singularity
If you are working on the same system where you will run Nextflow, you can amend the downloaded images to the ones
in the$NXF_SINGULARITY_CACHEDIR folder, Nextflow will automatically find them.However if you will transfer the
downloaded files to a different system then they should be copied to the target folder.
? Copy singularity images from $NXF_SINGULARITY_CACHEDIR to the target folder or amend new images to the cache? co
py
If transferring the downloaded files to another system, it can be convenient to have everything compressed in a
single file.
This is not recommended when downloading Singularity images, as it can take a long time and saves very little
space.
? Choose compression type: none
Workflow Execution - CLI Execution Profile
None
What happened?
I am trying to use nf-core to download the wf-human-variation workflow onto a cluster entry node so that I can run it on a compute node which does not have internet access. I input the above code and then run through the options below it to select the version, container images etc. However, when it tries to pull the singularity images, it fails and crashes. It seems that the command tries to look at an address in quay.io for the singularity image but can't find it, and when I go to that address on my browser there is nothing there either. When I run the individual command to pull the singularity image, as suggested in the error report, I get another error saying it failed to get the checksum and I am not authorised to access it. I did find docker images in different locations when searching manually e.g. at a different quay.io address and at a Docker hub address, but I don't know how to change this in the command. I am also not sure why it is pulling Docker images when I have asked for Singularity images.
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
The text was updated successfully, but these errors were encountered: