Closed pritampanda15 closed 2 months ago
Dear Pritam,
This pipeline is not a nf-core pipeline, thus it does not adhere to the nf-core standards completely. The mentioned image is a non-institutional. My suspect is it might be because of that. I think you can download docker images with
docker pull image
command. and then convert singularty later.
Best, Kubra
singularity pull --name /omics/groups/OE0526/internal/users/pritam/raredisease/singularity_image/kubran-odcf_mpileupsnvcalling-v0.img docker://quay.io/kubran/odcf_mpileupsnvcalling:v0
nf-core download command adds quay.io automatically, as I see. My docker images are in my own docker not in quay.io. since nf-core puts their docker images to quay.io, that apply to them only.
Therefore, what you can do download images one by one:
singularity pull --name /omics/groups/OE0526/internal/users/pritam/raredisease/singularity_image/kubran-odcf_mpileupsnvcalling-v0.img docker://kubran/odcf_mpileupsnvcalling:v0
Thank you @kubranarci. I will download the images manually as aforementioned.
Have you checked the docs?
Description of the bug
I have used nfcore-download command as suggested to pull the singularity images. But resulted in errors (see terminal outputs)
Command used and terminal output
Relevant files
No response
System information
Nextflow version 23.10.1 DKFZ Cluster Singularity CenOS