Open berguner opened 2 years ago
uff.. I wonder if we go back to using an nfcore
container for this. We're listed as OSS on docker-hub so shouldn't have any pull limits.
Alternatively we could use a mirror on quay.io as that's the same docker registry as biocontainers and shouldn't have pull limits. eg: https://quay.io/repository/bedrock/ubuntu
I guess it should be fine to use any linux image with md5sum in it. For example I was able to run it with tabix
image, which also has a small footprint. Below is the configuration that I used.
process {
withName: MD5SUM {
container = "quay.io/biocontainers/tabix:0.2.6--ha92aebf_0"
}
}
@matthdsm Any objections to using https://quay.io/repository/bedrock/ubuntu?
I don't really care which image you use, just make sure it's not some bloated mess so we can keep the download times low
With that, we could probably get away alpine for this task, but I'm thinking across the board whether that would work for these minimal containers
I agree with alpine! We'll have to make sure it uses the same algorithms for everything though, been burned on that before.
Description of the bug
Hi,
I was running the pipeline on AWS Batch and MD5SUM tasks failed due to docker pull limit. I assume this happens when there are more than ~100 FastQ files. It seems like this task was pulling the
ubuntu:10.04
image from Docker hub, so it can be fixed by pointing to an image onquay.io/biocontainers
.https://github.com/nf-core/demultiplex/blob/b0a004eb2e79f6fceb9b5d79b91b563b7724ed62/modules/nf-core/md5sum/main.nf#L8
Command used and terminal output
Relevant files
No response
System information
N E X T F L O W ~ version 22.04.5