Connections being closed

[kciredor]

Please reopen issue #1374 because it should not have been (auto) closed for the reason the bug is still there. For 3 years now, btw...

[stephen-turner]

Thanks for the report, @kciredor. That ticket wasn't autoclosed: it was closed by a developer on 26 Jul 2018. It seems that the original issue that lots of people were seeing was fixed at that time. There were only very occasional reports after that, so I think it must be a different issue.

So let's start again. Could you please describe the exact symptoms that you are now seeing, steps to reproduce, and include a diagnostics id? Thank you.

[kciredor]

Hi @stephen-turner thanks for your fast response! You are absolutely right, I was mistaken by the "docker locked and limited conversation to collaborators on 23 Jun" which I concluded to be auto-close too fast.

Will respond with additional info soon.

[kciredor]

I'm using the latest stable Docker for Mac, with default settings (also tried Docker RAM increment to 16gb) on the latest stable version of macOS.

From inside a container:

• Running "kops update cluster --yes" in a loop, which supports the "kops rolling-update cluster --yes" command on specifically OpenStack.
• "kops update cluster" generates tens of https GET/POST calls to the OpenStack and Swift API endpoints.
• After a while, "kops update cluster" will hang. This becomes worse over time (first few minutes it's fine, then everything slows down, eventually nothing comes through anymore). Adding verbosity will show you it stalls on those API calls.
• The OpenStack provider saw nothing special in the logs except for SSL timeouts. From my side I see I/O timeouts.
• Restarting Docker will fixes the problems.

On the other hand if I do the exact same things outside of a container, everything is fine, there is no way to trigger this problem even if I run 5x "kops update cluster --yes" in parallel.

My colleagues were able to reproduce as well. To be quite honest this feels similar to the closed #1374 which was locked.

Please forgive me in not dumping a diagnostics log as I'm not going to run cluster updates right now just for creating an issue, I hope you understand ;-)

Cheers!

[stephen-turner]

Thanks. Could you upload diagnostics when it next happens? We will need that in order to look at the logs. Thanks.

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days 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

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

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