Hi, I have a couple of linting warnings. Can you help me understand how to fix it? 1.

bbmaprepair  │ modules/local/bbmaprepair.nf │ Container versions do not match

The process begins:

process BBMAPREPAIR {

tag "$meta.id"

label 'process_single'

container '<http://docker.io/mazzalab/fastqrepair_nf_env:1.0.1|docker.io/mazzalab/fastqrepair_nf_env:1.0.1>'

Which versions were compared? 2.

bbmaprepair  │ modules/local/bbmaprepair.nf │ Unable to connect to container registry, code:  403, url: <https://www.docker.com/mazzalab/fastqrepair_nf_env:1.0.1>

What's the right URL to the dockerhub: https://hub.docker.com/r/mazzalab/fastqrepair_nf_env ? thanks

I used to get these warnings too but they are gone now. Your

container

directive looks fine. I think this was a temporary issue in

nf-core/tools

. Which

nf-core/tools

version are you using?

Hi Felix, I've nf-core/tools version 3.0.2

Ok, this may sound weird but the issue is the way that your modules are structured. Judging from your information, your local modules are structured like this:

modules/local/bbmaprepair.nf

The nf-core standard is:

modules/local/bbmaprepair/main.nf

I know this sounds unrelated to your problem but

nf-core/tools

can't properly handle your modules. I had a similar issue: https://nfcore.slack.com/archives/CE6PELWR4/p1724921668326519, fixing the module structure has also resolved the linter warning for docker containers (I just tested that).

OK, just let me follow your suggestion and get back to you.

Just keep in mind that this will require small changes to the include statements for these modules in your workflows.

already fixed everything