Daniel Lundin
03/10/2025, 10:29 AMbbmap/bbnorm module which has been converted to wave. Earlier, it was using a mulled container. What should I do to update one of the tools in the container? The conda and conatiner lines of the module now looks like:
conda "${moduleDir}/environment.yml"
container "${ workflow.containerEngine == 'singularity' && !task.ext.singularity_pull_docker_container ?
'oras://community.wave.seqera.io/library/bbmap_samtools_pigz:2a066f0214cc5eb0' :
'community.wave.seqera.io/library/bbmap_samtools_pigz:79703e935236b43b' }"
bbmap_samtools_pigz was our name of the mulled container. And I've updated the environment.yml to:
---
# yaml-language-server: $schema=https://raw.githubusercontent.com/nf-core/modules/master/modules/environment-schema.json
channels:
- conda-forge
- bioconda
dependencies:
- bioconda::bbmap=39.18
- pigz=2.8
(The update was 39.17 to 39.18.)
Wave is supposed to build containers for us, right? Is it relying on the environment.yml? Should I replace the two container urls somehow to trigger an automatic build of a new container?Matthias De Smet
03/10/2025, 10:33 AMenvironment.yaml file and then feed that to the wave-cli to generate a new containerMatthias De Smet
03/10/2025, 10:34 AMMatthias De Smet
03/10/2025, 10:34 AMDaniel Lundin
03/10/2025, 10:51 AMwave commands and pasted the resulting two urls in main.nf.
wave --conda-file modules/nf-core/bbmap/bbnorm/environment.yml
wave --freeze --singularity --conda-file modules/nf-core/bbmap/bbnorm/environment.ymlMatthias De Smet
03/10/2025, 10:53 AMDaniel Lundin
03/10/2025, 10:53 AMMatthias De Smet
03/10/2025, 10:58 AMoras oneDaniel Lundin
03/10/2025, 11:00 AMoras url before updating (done by someone else) and got only an oras from the command. I'll see how it goes.Matthias De Smet
03/10/2025, 11:01 AMDaniel Lundin
03/10/2025, 11:02 AMoras didn't work, nor did just naively replacing oras with https.Matthias De Smet
03/10/2025, 11:04 AMMatthias De Smet
03/10/2025, 11:04 AMDaniel Lundin
03/10/2025, 11:16 AM