Open nh13 opened 5 years ago
Hi @nh13, not from Broad but have you tried turning the docker-digest lookup off with the following in your config:
docker.hash-lookup.enabled = false
I'm having the same issue, is there any solution other than docker.hash-lookup.enabled = false
because it may cause problems for call caching
I am also encountering this issue and have yet to find resolution.
I think call caching can't work on images without a hash/digest anyway, since the hash is taken into account to evaluable caching eligibility.
I am trying to run Cromwell with docker images that were loaded with
docker load
. This means that the digests are unavailable (i.e.<none>
). Unforutnately, this means that when looking up the image locally (i.e. when the configdocker.hash-lookup.method="local"
is used), the image is not found. The offending lines of code are: https://github.com/broadinstitute/cromwell/blob/1898d8103a06d160dc721d464862313e78ee7a2c/dockerHashing/src/main/scala/cromwell/docker/local/DockerCliClient.scala#L26 https://github.com/broadinstitute/cromwell/blob/1898d8103a06d160dc721d464862313e78ee7a2c/dockerHashing/src/main/scala/cromwell/docker/local/DockerCliClient.scala#L78-L92Can we instead use the image ID instead of the digest when using local images?
log output
``` [INFO] [09/16/2019 11:07:14.821] [cromwell-system-akka.dispatchers.engine-dispatcher-40] [akka://cromwell-system/user/SingleWorkflowRunnerActor/JobExecutionTokenDispenser] Not triggering log of token queue status. Effective log interval = None [INFO] [09/16/2019 11:07:14.830] [cromwell-system-akka.dispatchers.engine-dispatcher-76] [akka://cromwell-system/user/SingleWorkflowRunnerActor/JobExecutionTokenDispenser] Assigned new job execution tokens to the following groups: 2b766fe6: 1 [2019-09-16 11:07:16,20] [error] Docker pull failed java.lang.RuntimeException: Error running: docker pullA workaround is setting up a registry to host the images (so we can have digests), but I ask anyway.