[
https://issues.apache.org/jira/browse/BEAM-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771762#comment-16771762
]
Matt Casters commented on BEAM-6706:
------------------------------------
For my dependencies I just moved from 2.9.0 to 2.10.0. I confirmed again that
my test-jobs run fine on 2.9.0 and not on 2.10.0.
Is there anything specific I need to check wrt the changes in guava or gRPC?
>From the release notes I saw the following:
* Java: Migrate to vendored gRPC (no conflicts with user gRPC, smaller jars)
* Java: Migrate to vendored Guava (no conflicts with user Guava, smaller jars)
Kettle Beam looks at a few runners and dependencies and this is what I'm seeing
right now in my libraries:
```
beam-vendor-guava-20_0-0.1.jar
flink-shaded-guava-18.0-2.0.jar
guava-27.0-jre.jar
jersey-guava-2.22.2.jar
listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar
```
So moving forward under the assumption I'm the person in the wrong here, not
the Beam project itself, the next best thing would be to figure out the best
way to debug the situation. Any tips are welcome.
> 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: Kenneth Knowles
> Priority: Blocker
>
> 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)
