Closed klamkiew closed 1 year ago
Argh, what's going on with all theses condo envs ^^ damn it
Sigh https://github.com/sanger-pathogens/Roary/issues/585 It's not me/us - seems to be a general issue.
Funnily enough, I can resolve the env with mamba... not sure why conda is having issues here.... maybe we can plug in mamba into NF, even though it is experimentally? @hoelzer ever done this before? :D
Yes Mamba profiles work, Marie implemented one in... Clean I think? Or rnaflow? We can ask her and c&p ;)
And strange the roary condo thing... Good we build also a container 3y ago ^^
Once I find some time, I'll try to dig deeper into that issue; for now, maybe the mamba fix is already sufficient. But we also had issues with the prokka env, so I think there might be some underlying conda config problem :/
Alright; I set useMamba = true
in the conda scope of our nextflow config. Now, one has to have nextflow and mamba, if one wants to use conda, but this isn't much of a hussle with conda anyways.
Closing this for now -- I still have to check whether a switch between conda and mamba is possible (e.g. a profile mamba, that looks like conda but uses mamba)
great thx!
Honestly, for me it's also totally fine if the user needs nextflow +
and conda is not natively supported. Of course, if we can have a profile that looks like conda but just installs and uses mamba: fine ;) But maybe not worth the hazzle
Use Mamba to resolve packages It is also possible to use mamba to speed up the creation of conda environments. For more information on how to enable this feature please refer to Conda.
Warning This feature is experimental and may change in a future release.
https://www.nextflow.io/docs/edge/conda.html#use-mamba-to-resolve-packages Fingers are crossed, nothing too dramatically changes ;) I agree with you, but we should keep it in mind.
see title, I am working on it ;)