weird behavior during log wait condition on during container start #344
Description
so this is a fun one...
it seems like every so often, something is interrupting the stream returned from docker while waiting on a log condition. the annoying things is, i have no real test case that can easily reproduce this.
it seems to occur at random during a rather large monolithic build. each project that needs the container starts one, which in turns causes a bunch of sql scripts to run which take ~30s or so.
basically the read call is blocking on data it expects to be there, but isn't. i'm kind of at a loss as to what could be causing this b/c it just fails at random times on an operation that has been successful before. when running w/ the -X option, there it's also random as to where in the logs the stream cuts out.
any thoughts on this? i'm gonna play around in the logging code tomorrow and turn up docker's logging to see if it will tell me anything useful.