This repository has been archived by the owner on Jul 2, 2023. It is now read-only.
Add ignoreeof flag to socat tcp listener
#22
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After a maddening few hours of using `socat` as a proxy to the docker socket and wondering why `docker run` would inconsistently fail to return any output I found it was due to the unfortunate behaviour of `socat` and the `docker` cli. I believe that the docker client is leaving the socket half-open which triggers socat to timeout (after 0.5s by default) if there is no data to read from the opposite direction. Increasing the timeout (`socat -t10`) worked but ignoring the EOF entirely seems more robust.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After a maddening few hours of using
socatas a proxy to the docker socket and wondering whydocker runwould inconsistently fail to return any output I found it was due to the unfortunate behaviour ofsocatand thedockercli.I believe that the docker client is leaving the socket half-open which triggers socat to timeout (after 0.5s by default) if there is no data to read from the opposite direction. Increasing the timeout (
socat -t10) worked but ignoring the EOF entirely seems more robust.