Skip to content

Conversation

@djs55
Copy link
Collaborator

@djs55 djs55 commented Aug 10, 2017

Previously we would timeout switch ports after 300s of inactivity. Ideally active connections would be configured to send keep-alive packets sooner than this. To better support cases with no keep-alives, it's useful to be able to reconfigure the idle timeout (e.g. to make it much bigger or disable it altogether).

This patch adds

  • a command-line argument --port-max-idle-time
  • a database key slirp/port-max-idle-time

which allow the default 300s to be overriden. Values <= 0 disable the timeout mechanism completely.

Related to #235
Related to #234

djs55 added 3 commits August 10, 2017 12:14
Previously we would timeout switch ports after 300s of inactivity.
Ideally active connections would be configured to send keep-alive packets
sooner than this. To better support cases with no keep-alives, it's
useful to be able to reconfigure the idle timeout (e.g. to make it
much bigger).

This patch adds

- a command-line argument `--port-max-idle-time`
- a database key `slirp/port-max-idle-time`

which allow the default 300s to be overriden.

Related to moby#235
Related to moby#234

Signed-off-by: David Scott <[email protected]>
This allows us to completely disable the mechanism by setting the
port-max-idle-time to 0 (or -ve)

Signed-off-by: David Scott <[email protected]>
Previously using a text editor might result in a string like
`1\n` which would be rejected. This patch trims the unnecessary
whitespace from the beginning and end of ints and bools so this
string will be parsed as `1`.

Signed-off-by: David Scott <[email protected]>
@ltammariello
Copy link

How do you set this value on Docker for Windows?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants