[
https://issues.apache.org/jira/browse/BEAM-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774945#comment-16774945
]
Matt Casters commented on BEAM-6706:
------------------------------------
I took note of the false flag and will investigate further, thanks for the
information!
To be fair, in my original mail to the Beam user mailing list I already assumed
it was my own fault. I was just looking for pointers as to what actually might
be different between 2.9 and 2.10 in terms of dependencies and/or setup. I
will focus on that aspect now.
I will report back once I found the culprit.
> User reports trouble downloading 2.10.0 Dataflow worker image
> -------------------------------------------------------------
>
> Key: BEAM-6706
> URL: https://issues.apache.org/jira/browse/BEAM-6706
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Kenneth Knowles
> Assignee: Matt Casters
> Priority: Major
>
> DataFlow however is throwing all sorts of errors. For example:
> * Handler for GET
> /v1.27/images/gcr.io/cloud-dataflow/v1beta3/beam-java-batch:beam-2.10.0/json
> returned error: No such image:
> gcr.io/cloud-dataflow/v1beta3/beam-java-batch:beam-2.10.0"
> * while reading 'google-dockercfg' metadata: http status code: 404 while
> fetching url
> http://metadata.google.internal./computeMetadata/v1/instance/attributes/google-dockercfg";
> * Error syncing pod..."
> The job gets stuck after starting a worker and after an hour or so it gives
> up with a failure. 2.9.0 runs fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
