Is there a way to force nextflow to use a container instead of conda when both are enabled? I read that that's supposed to be the default, but it's not what I'm seeing. I need conda enabled because one of my processes needs it but I prefer for everything else to use singularity. However, when I enable conda my nf-core modules try to build a conda environment (and fail because of an unrelated storage issue) instead of using singularity, and when I disable conda, it uses singularity and is happy. But then the one process that needs conda fails. Is there a setting somewhere that I'm overlooking?

How are you doing the enabling? The default nf-core pipelines for example use profiles, where each different containerisation profile explicitly disables the other containerisation tools. I believe if you use an environment yaml and wave you can also technically have nextflow build the container on the fly for that process but I find wave a bit esoteric and opaque honestly