A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

NF-CORE NOT SUPPORTING CONDA LOCK FILES :shakefist::shakefist::shakefist:

soon ™ <https://github.com/nf-core/tools/pull/3954>

if you want you can already try out on the module in question

See also these <https://nf-co.re/blog/2024/seqera-containers-part-1#exceptionally-reproducible|blog> <https://nf-co.re/blog/2024/seqera-containers-part-2#conda-lock-files|posts>

and <https://seqera.io/blog/ensuring-consistent-behavior-across-conda-and-docker-environments-with-wave/>

(the blog link would have been on my bingo card :grin: )

see also <https://nf-co.re/hackathon-projects/hackathon-march-2026/container-conversion>

A little doubt about this came to my mind: how would this work for packages resolved dynamically by device capabilities (basically CUDA)? Generating the lock on a CUDA-enabled device will create an incompatible environment for CPU-only devices? :thinking_face:

The conda lock files come from the docker-build environments (they're basically a snapshot of the docker container conda install)