Is there a way to force Seqera Containers to rebuild a container? I am trying to retrieve one for ont-modkit version 0.5.0. The Singularity container works fine but modkit identifies itself as version 0.4.5 instead of 0.5.0 in the Docker container. See Container build report
Hi @Schmytzi,
Thanks for flagging this! The version mismatch was caused by a bug in the Bioconda recipe, which has since been fixed (bioconda-recipes#57596). Unfortunately, the container was already cached on Seqera Containers before the fix landed, so it picked up the incorrect version.
We’ll trigger a rebuild of the ont-modkit 0.5.0 Docker image and let you know here once it’s available.
EDIT: It’s been rebuilt now with this container URI: community.wave.dev-seqera.io/library/ont-modkit:0.5.0--d3e9220294cb8cba. We’re working on having it on Containers | Seqera too.
Hi @Schmytzi
We now allow users to edit the environment.yaml on Seqera Containers so that you can pick different builds from the same package version 
See a short video at #containers #conda #nowyouknow | Phil Ewels about it.
The new Seqera Containers container image for ont-modkit 0.5.0 (that is really 0.5.0) is community.wave.seqera.io/library/ont-modkit:0.5.0--a3ce75f825550ab8