Networking timeouting after certaing amount of delay

[jtiai]

• [x ] I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID:

Problem appears everytime. I'm trying to load bunch of data from remote database to local database (Oracle). There is one step that takes long time at remote end to produce and connection is closed meanwhile.

• Windows Version: Windows 10 Pro, 1803 build 17134
• Docker for Windows Version: 2.0.0.0-beta1-win75 (Tried with stable as well)

There was mention that this is fixed in 17.07.0-rc3 but I couldn't find any information how to set this value in configuration.

VPNKit: Added slirp/port-max-idle-timeout to allow the timeout to be adjusted or even disabled

[jessetan]

Looks similar to moby/vpnkit#414

The setting you mention can be changed on macOS, but not on Windows as far as I can tell, see docker/for-mac#2197 (comment)

[gfalcone]

Hi, I am having the same issue with Docker for Windows 2.0.0.2. Is there any update on this ?

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[markus-ksg]

/remove-lifecycle stale

[markus-ksg]

/lifecycle frozen

Still broken on Windows and still annoying. My Xdebug sessions are always terminated automatically after 5 minutes without interaction.

[ltammariello]

Looks similar to moby/vpnkit#414

The setting you mention can be changed on macOS, but not on Windows as far as I can tell, see docker/for-mac#2197 (comment)

Any info. on how to set the port_max_idle_time value on Windows?

[mbilal100]

I'm having the same problems that is TCP connection loses while at idle after 5 minutes

[mbilal100]

It looks like slirp/port-max-idle-timeout option had been added for this issue as 359 but later this change had been reverted due to reduce the memory usage 389
@djs55 can you please confirm above?
Can we disable default ~300s TCP timeout in any way on Windows?

[djs55]

@mbilal100 I don't think it's currently possible to change the default timeout on Windows. It requires adding the option --port-max-idle-time <time in seconds> to the vpnkit command-line, however vpnkit is spawned directly by the Docker Desktop app. I don't know if there is a Windows equivalent to the old Unix trick of replacing a binary with a shell script which adjusts the arguments.

I've made an internal ticket noting this problem and will discuss it with my colleagues. Thanks for the report, sorry I don't have better news.

[mhussein]

Still facing this issue on windows, it is very annoying. Has anyone found a workaround for it, or are there any plans to get it fixed?

[tsiddiq]

Checked with latest docker version (3.1.0), it is still broken on Windows and still annoying.

[JialeCao]

Does anyone have workaround solution? I still facing this issue on windows.

[JialeCao]

@mbilal100 I don't think it's currently possible to change the default timeout on Windows. It requires adding the option --port-max-idle-time <time in seconds> to the vpnkit command-line, however vpnkit is spawned directly by the Docker Desktop app. I don't know if there is a Windows equivalent to the old Unix trick of replacing a binary with a shell script which adjusts the arguments.

I've made an internal ticket noting this problem and will discuss it with my colleagues. Thanks for the report, sorry I don't have better news.

@djs55 May I ask you about this issue? Could you share some information about your internal ticket? Thank you in advance!

[dlangeland]

I think I've found the solution...

1. Stop Docker Desktop - wait for it to completely stop
2. In C:\Users\%USER%\AppData\Roaming\Docker\settings.json change the value of vpnKitMaxPortIdleTime to 0
3. Start Docker Desktop
4. Validate that vpnKitMaxPortIdleTime is still 0

It now works. It might only work in recent versions.

[deni-cm]

@dlangeland

Can confirm that this is working @ Windows 10, WSL2, Docker Desktop v4.12.0
Fixes the issues with docker dropping azure's key-vault idle connection after 300sec :)