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

nf-core

Hi, has anyone tried provisioning a wave container from a conda channel other than `bioconda` or `conda-forge` ? What did the `nf-core modules lint` have to say about it? We are running into the following issue <https://github.com/nf-core/tools/issues/3499>

Hi <@U06GQDF1UJW>, nf-core linting doesn't allow other channels currently

<@UE4L64T4G> <@UQZG2UCF3> anyone else from <#C069B2Z5P1R|>, should we allow more conda channels?

Hi <@U02JS8EFMMJ>! Thanks for this - so there is different behaviour - wave containers allow any channel, but the linter hasn't quite caught up with this. What would you recommend? Open a PR to change the behaviour of the linter, or ignore the warning in the linter for now? Happy to have a call if it's easier :slightly_smiling_face:

I would say ignore the warning in the linter for now

I think we have to discuss if we include other channels first

This is sort of a feature, not a bug. It's comparable to use not wanting random docker accounts to be used. 

Sticking to known conda channels increases the chance of stability and long term maintenance, as well as giving us containers for free via bioconda (though this becomes a lot less important once we fully migrate to wave)

But we should maybe reconsider now that we have more imaging pipelines etc, where bioconda seems to be less prevalent. 