<- Has anyone seen this in their (docker) agent output. It happened after two frames of stacktrace for me, on a mapped task (149 of 876), and the agent stopped processing anything (or sending anything to stdout anyway, and the rest of the tasks didn't run).
Grepping for "grabbing logs" turns up nothing in the prefect repo, our own code, or any of the dependencies in my virtualenv. It's a cloud-backed flow run; is this coming from cloud, maybe?
k
Kevin Kho
07/20/2021, 2:47 PM
Hey @Michael Warnock, I haven’t seen this before. It looks more of a Docker error, but I wouldn’t know where to start. This Github issue has the same post but no solution.
Kevin Kho
07/20/2021, 2:48 PM
This person said they experienced it on 20.10.1, so they reverted to 19.03.14. What is your Docker version?
m
Michael Warnock
07/20/2021, 2:50 PM
20.10.0 - should have realized it was docker; thanks!
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.