google/deepvariant:1.6.1 docker says version 1.6.0 about deepvariant HOT 3 OPEN

@fellen31 ,

version 1.6.1 had a very small incremental change and the docker version was not updated. I can confirm that 1.6.1 docker has the code change required but the version update for printing the version wasn't changed. Is this a blocking issue for you? Otherwise we will update it the next version appropriately in the next release.

from deepvariant.

I'd say it's mostly because the VCF also says ##DeepVariant_version=1.6.0, which could be confusing. If it's not too much of a hassle to rebuild 1.6.1 and 1.6.1-gpu so they output the correct version, I think that would be great. Otherwise I could always refer to this issue.

from deepvariant.

Hi @fellen31 ,

Thanks for the suggestion. For the official Docker file, we usually don't like to modify it after we push it. This is mostly for reproducibility concern. Even when we don't change everything else on our side, rebuilding at a later time can cause confusion if some other components (not in our control) has changed, and then might result in unexpected reproducibility differences.

A few possible solutions:

1. We'll make sure to update the version number in future releases, and we'll be careful even with a PATCH version update. (But we'll do nothing right now)
2. Or, if it's absolutely necessary for you to access a Docker under our Docker Hub and/or gcr.io, I can build one for you, but it will be called something like 1.6.1-fix-version (instead of overwriting the 1.6.1 images).

To do 2, it will take some time and effort on my side, but it's doable if it's important for you. Let me know!

from deepvariant.