We've moved!
For WDL questions, see the WDL specification and WDL docs.
For Cromwell questions, see the Cromwell docs and please post any issues on Github.

"Docker lookup failed" when running Cromwell on Google VM

I ran into a problem when moving cromwell (cromwell-32) execution of a wdl pipeline from a local computer (Mac) to a VM on google that runs Ubuntu. The wdl pipeline pushes tasks to the google cloud, which works fine on my local machine. It fails on the google VM. I tried running the same wdl pipeline with the same container located at gcr and docker.

I am getting a following error for a container stored at gcr:

2018-06-14 23:21:00,130 WARN  - BackendPreparationActor_for_c3101801:XXX.yyy:1:1 [UUID(c3101801)]: Docker lookup failed
java.lang.Exception: Timeout looking up docker hash
[...]
2018-06-14 23:21:36,543 ERROR - PipelinesApiAsyncBackendJobExecutionActor [UUID(c3101801)BOTA.prodigal:2:1]: Error attempting to Execute
cromwell.core.CromwellFatalException: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

and a following error for a container stored at docker hub:

2018-06-14 22:41:49,541 WARN  - BackendPreparationActor_for_7a49828d:XXX.yyy:6:1 [UUID(7a49828d)]: Docker lookup failed
java.lang.Exception: Failed to get docker hash for biojokke/bota:3aaa7b1094161232a3bf860a7cc9f3cc8a417789 Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
[...]
2018-06-14 22:42:25,896 ERROR - PipelinesApiAsyncBackendJobExecutionActor [UUID(7a49828d)BOTA.prodigal:1:1]: Error attempting to Execute
cromwell.core.CromwellFatalException: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

In case of the run with container at gcr, cromwell hangs for a few minutes before spitting out the error, while the error for the container at docker appears right away.

It could be that I am missing a step for properly setting up the VM. Any ideas?

Answers

Sign In or Register to comment.