Current default behavior is to use the latest image tag for the SPT docker image in Singularity and Docker Nextflow workflows, but we observed an issue where Singularity doesn't check for later latest images; so long as you've ever downloaded and cached a latest image, it'll be used, even if it's far from the latest version of latest. To avoid this, we should simply pin the version of the SPT image used, or establish it to be whatever the version of SPT is being used to write the configure command.
CarlinLiao
commented
3 months ago
Current default behavior is to use the
latestimage tag for the SPT docker image in Singularity and Docker Nextflow workflows, but we observed an issue where Singularity doesn't check for laterlatestimages; so long as you've ever downloaded and cached alatestimage, it'll be used, even if it's far from the latest version oflatest. To avoid this, we should simply pin the version of the SPT image used, or establish it to be whatever the version of SPT is being used to write the configure command.