Closed aidan-mundy closed 2 years ago
After digging a bit deeper into the code, this error is caused by the initial SIGWINCH
signal sent immediately after starting the container when running runContainer()
. The container must be exiting before the signal is fully handled (further evidenced by the error message associated with docker API error 409: "Can not reuse socket after connection was closed."). The error does not cause the job to fail, it only appears to print.
My suggestion here is to change the Error
message to a Warning
. I will put a PR up for this change.
Job commands that cause the container to exit too quickly cause errors like this one:
This causes the(This might not be true actually, my test failure may be coming from a different cause, but theinit-named-volume
example/integration test to fail because the copy and touch commands run near-instantly.ERROR
message still appears.) Brief testing shows that the minimum stable command length on my machine is 10 ms.If a solution to this error cannot be found, a
sleep 0.1s
should be added to thepopulate
job'scommand
ininit-named-volume
.