Fixes #10387 Without TCP keep-alive set on socket connections to the daemon, any long-running container with std{out,err,in} attached that doesn't read/write for a minute or longer will end in ECONNTIMEDOUT (depending on network settings/OS defaults, etc.), leaving the docker client side believing it is still waiting on data with no actual underlying socket connection. This patch turns on TCP keep-alive for the underlying TCP connection for both TLS and standard HTTP hijacked daemon connections from the docker client, with a keep-alive timeout of 30 seconds. Docker-DCO-1.1-Signed-off-by: Phil Estes <estesp@linux.vnet.ibm.com> Upstream-commit: f73a6b3845a498107cfb22e4d962f0a30870e7c6 Component: engine
This directory contains code pertaining to the Docker API:
-
Used by the docker client when communicating with the docker daemon
-
Used by third party tools wishing to interface with the docker daemon