I updated a module where the most recent version of the tool is only available via pip and needs some more dependencies installed to work via the pip installation. To use the most recent version of the tool I created wave containers that combine all tools necessary for the use and the tool itself. When I lint the module I get:

╭─ [!] 2 Module Test Warnings ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                    ╷                                           ╷                                                                                                                                                                                                    │
│ Module name        │ File path                                 │ Test message                                                                                                                                                                                       │
│╶───────────────────┼───────────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╴│
│ crabs/insilicopcr  │ modules/nf-core/crabs/insilicopcr/main.nf │ Unable to connect to container registry, code:  404, url: <https://community.wave.seqera.io/library/cutadapt_muscle_vsearch_wget_pruned:04f6c0370c0226c5>                                            │
│ crabs/insilicopcr  │ modules/nf-core/crabs/insilicopcr/main.nf │ Container versions do not match                                                                                                                                                                    │
│                    ╵                                           ╵                                                                                                                                                                                                    │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

When I check, the container is available. Does anyone know what is going on here?

I don't think it should have a

https://

prefix - did you add that?

No I did not add that. I think its the docker container that is mentioned.

Where did you get the URL from?

From the web interface, this is how it looks in the module:

container "${ workflow.containerEngine == 'singularity' && !task.ext.singularity_pull_docker_container ?
        '<oras://community.wave.seqera.io/library/cutadapt_muscle_vsearch_wget_pruned:0cd5cb1e549e5033>':
        '<http://community.wave.seqera.io/library/cutadapt_muscle_vsearch_wget_pruned:04f6c0370c0226c5|community.wave.seqera.io/library/cutadapt_muscle_vsearch_wget_pruned:04f6c0370c0226c5>' }"

ok werid, then I'm not sure as that looks fine

Both of those are warnings so I was just curious why the container would not be found even though I can pull it locally and also the web interface says the build was successful

Can maybe repost to #CJRH30T6V as I know others have done it

Yeah I am probably going to leave it as is for now.

Why are the checksums different ?

0cd5cb1e549e5033

vs

04f6c0370c0226c5'

Singularity vs Docker - they are separate builds

ty