Setshaba
05/23/2024, 10:05 AMMay-23 11:27:28.959 [Actor Thread 17] INFO nextflow.container.SingularityCache - Pulling Singularity image docker://ontresearch/wf-human-variation-snp:sha6d5c80963ce346695d98205563c87dc71fc182ff [cache /mnt/lustre/users/staukobong/work/singularity/ontresearch-wf-human-variation-snp-sha6d5c80963ce346695d98205563c87dc71fc182ff.img]
May-23 11:28:29.002 [Actor Thread 19] DEBUG nextflow.processor.TaskProcessor - Handling unexpected condition for
task: name=ingress:checkBamHeaders (1); work-dir=null
error [java.lang.IllegalStateException]: java.lang.IllegalStateException: Failed to pull singularity image
command: singularity pull --name ontresearch-wf-common-sha91cd87900c86f05bf36d8c77b841b8fda5ecf3aa.img.pulling.1716456448959 docker://ontresearch/wf-common:sha91cd87900c86f05bf36d8c77b841b8fda5ecf3aa > /dev/null
status : 255
message:
[31mFATAL: ^[[0m While making image from oci registry: failed to get checksum for docker://ontresearch/wf-common:sha91cd87900c86f05bf36d8c77b841b8fda5ecf3aa: pinging docker registry returned: Get https://registry-1.docker.io/v2/: dial tcp 54.236.113.205:443: i/o timeout
Does anyone perhaps know how I can work around this? Some help would be greatly appreciated.pontus
05/23/2024, 10:11 AM-profile test,singularity on one node that has connectivity and making sure to use a cachedir for singularity.James Fellows Yates
05/23/2024, 10:25 AMJames Fellows Yates
05/23/2024, 10:25 AMSetshaba
05/23/2024, 11:12 AM