This relates to changing the docker config so, it uses docker shasum instead of tags, meaning that we can ensure that the pipeline always runs with the exact version of the docker image.
Sometimes, a docker image using a tag, can be updated due to bug fixes as happened in #96 however, if already available in the user's system, nextflow will not try to download it again.
However, using docker shasum, we can ensure making the pipeline always use the exact version of the pushed image, thus, guaranteeing automatic update by nextflow if a bugfix is made, even if the same tag is already available, however, with a different shasum, it is not considered the same for the pipeline.
This relates to changing the docker config so, it uses docker shasum instead of tags, meaning that we can ensure that the pipeline always runs with the exact version of the docker image.
Sometimes, a docker image using a tag, can be updated due to bug fixes as happened in #96 however, if already available in the user's system, nextflow will not try to download it again.
However, using docker shasum, we can ensure making the pipeline always use the exact version of the pushed image, thus, guaranteeing automatic update by nextflow if a bugfix is made, even if the same tag is already available, however, with a different shasum, it is not considered the same for the pipeline.
E.g.
form this