hash for call-caching should be from RepoDigest?

esalinasesalinas BroadMember, Broadie ✭✭✭

I have seen cases where the hash from the ID is different than the hash in the RepoDigest.

In such cases is it correct to put the RepoHash instead? (assuming a push to the repo has been done?)

I tried with the "Id" hash but got an error, but then got success with RepoDigest.

wm8b1-75c:workflows esalinas$ docker inspect broadinstitute/lego_plotter:1|head -20
[
    {
        "Id": "sha256:5b3b46748546be5bc75f07db7546efaacc8e3b6bfd9a9e27465bdd72039504a5",
        "RepoTags": [
            "broadinstitute/lego_plotter:1",
            "broadinstitute/lego_plotter:latest",
            "eddiebroad/lego_test:latest"
        ],
        "RepoDigests": [
            "broadinstitute/[email protected]:3db5a889236d5c01e81dfc7020fcc36432ec55ac712d66d72c76b118cdd24bb4",
            "eddiebroad/[email protected]:3db5a889236d5c01e81dfc7020fcc36432ec55ac712d66d72c76b118cdd24bb4"
        ],

Issue · Github
by Geraldine_VdAuwera

Issue Number
1929
State
closed
Last Updated
Assignee
Array
Milestone
Array
Closed By
vdauwera

Best Answer

Answers

Sign In or Register to comment.