docker-proxy-close-dangling-sockets

[meermonster10]

Make docker-proxy more resilient to CLOSE_WAIT and FIN_WAIT2 socket states.
In case of unexpected connection terminations, do not wait indefinitely until both ends are closed.
Signed-off-by: Jason Kim [email protected]

[GordonTheTurtle]

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:

$ git clone -b "patch-1" [email protected]:meermonster10/libnetwork.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

[Zer0t3ch]

ss is showing my server full of CLOSE-WAIT connections from docker-proxy causing kernel TCP out of memory. Would this modification presumably solve that problem, and when could we expect it to hit stable?

[Atl4sx]

+1

[litzk]

+1

[cpuguy83]

Note we have migrated this codebase over to github.com/moby/moby/libnetwork.
We are not accepting PR's on this repo anymore except for backports to be included in moby 20.10