With latest master the problem seems fixed. Unfortunately that was first
masked by build and docker issues. But I changed multiple things at once
after getting nowhere (the container build "succeeded" when in fact it
* Update to latest docker
* Increase docker disk space after seeing a spurious, non-reproducible
message in one of the build attempts
* Full clean and manually remove Go build residuals from the workspace
After that I could see Go and container builds execute differently
(longer build time) and the result certainly looks better..
On Sun, Nov 18, 2018 at 2:11 PM Ruoyun Huang <ruoyun@xxxxxxxxxx
I was after the same issue (I was using reference runner job server,
but same error message), had some clue but no conclusion yet.
By retaining the container instance, error message says "bad MD5"
(see the other thread  I asked in dev last week). My hypothesis,
based on the symptoms, is that the underlying container expects an
MD5 to validate staged files, but job request from python SDK does
not send file hash code. Hope someone can confirm if that is the
case (I am still trying to understand how come dataflow does not
have such issue), and if so, the best way to fix it.
On Fri, Nov 16, 2018 at 7:06 PM Thomas Weise <thw@xxxxxxxxxx
Since last few days, the steps under
The gradle task hangs because the job server isn't able to
launch the docker container.
[CHAIN MapPartition (MapPartition at
FlatMap (FlatMap at
- Still waiting for startup of environment
worker id 1
Unfortunately this isn't covered by tests yet. Is anyone aware
what change may have caused this or looking into resolving it?