disks: "local-disk 256 HDD"
This would be useful for forcing versioning of the docker image in the snapshot.
Hi @ilya_at_vivid ,
You can specify a docker with:
a tag like mentioned abovedocker: “broadinstitute/gatk:18.104.22.168”
a hash like shown heredocker: "[email protected]:71cd81252a3563a03ad8daee81047b62ab5d892ebbfbf71cf53415f29c130950"
docker: "[email protected]:71cd81252a3563a03ad8daee81047b62ab5d892ebbfbf71cf53415f29c130950"
@ilya_at_vivid Yes, you can add a hash like so:
docker: “broadinstitute/gatk:22.214.171.124” where the 126.96.36.199 is the hash.
What if you have a tag and a hash?
I had an error message with an "@hash after image name. Maybe that is the right format?
@ilya_at_vivid I don't believe that you can implement the hash from a runtime attribute. When you refer to hash do you mean the container ID as if two different containers were built from the same docker image?
Here is an example from a log file generated by terra. sha256 tag after the image name. I modified it to protect any identity. If a snapshot contained that hash you would guarantee that someone could not change the docker image in the snap shot. Right now I can just upload an image to a docker repository and the snap shot is no longer a "snap shot".
Pulling image "gcr.io/project/[email protected]:96a21410f3a03c44rtt67f9eaafd3165f1482f8ba2a92d4f9378504d9befb01"
2019/05/08 03:01:37 I: Pulled image "gcr.io/project/[email protected]:96a21410f3a03c44rtt67f9eaafd3165f1482f8ba2a92d4f9378504d9befb01"