Network connectivity issues. Docker restart is required.

[h3x00r]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: E37A2253-E455-4415-8FED-32401200765B/20190501031448
• Second Diagnostics ID: E37A2253-E455-4415-8FED-32401200765B/20190501041509

Expected behavior

Network connection to any container should not be lost randomly.

Actual behavior

Network connection to any container is lost. The necessary amount of time for this to happen
varies from few minutes to few hours. Docker restart is required.

Information

• Is it reproducible? Yes
• Is the problem new? No
• Did the problem appear with an update? No, it is since installation
• macOS Version: 10.14.4

Diagnostic logs

Docker for Mac: Version 2.0.0.3 (31259) without Experimental features enabled

Steps to reproduce the behavior

1. Have few containers up representing various projects i.e. 1 x magento2, 3 x laravel/lumen, 1 x mysql, 1 x redis, 1 x rabbitmq etc.
2. On host have nginx as proxy
3. Debug any project
4. Randomly the network connectivity (to containers) is lost.

[h3x00r]

Another Diagnosing ID

E37A2253-E455-4415-8FED-32401200765B/20190501113515

[h3x00r]

Another Diagnosing ID

E37A2253-E455-4415-8FED-32401200765B/20190501115324

[h3x00r]

Another Diagnosing ID

E37A2253-E455-4415-8FED-32401200765B/20190501124806
E37A2253-E455-4415-8FED-32401200765B/20190501142255
E37A2253-E455-4415-8FED-32401200765B/20190502034125

[h3x00r]

This is getting very annoying... restarts everywhere!

E37A2253-E455-4415-8FED-32401200765B/20190508110201

[hughsw]

See also #3487

[randrus]

See also 850A8A7D-C993-4C0B-AAE0-A411FA6C420B/20190718002153

[rnorth]

By connectivity is lost, what do you mean specifically? e.g. if you use netcat/telnet to try and communicate with running containers, do you:

(a) get an immediate connection refused failure; or
(b) manage to open a connection, but one that is essentially 'hung' (no data actually reaches the container)

I'm trying to determine whether or not to raise a new issue here in relation to:

• Docker for Mac - cannot connect to Ryuk testcontainers/testcontainers-java#1623
• https://forums.docker.com/t/port-forward-not-working-on-a-macos-installation-but-works-on-others/77401

[hughsw]

In #3487 we saw a third behavior:
(c) connection times out -- "Note: The connections to the containers time out, they are not refused."

Also, #3487 (comment) says:
"I believe the bug is fixed in current edge (Version 2.0.5.0 (35318))."

[randrus]

Sorry - didn't try that so I don't know - but I will try that next time it occurs and update here.

…

On Thu, Jul 18, 2019 at 4:30 AM Richard North ***@***.***> wrote: By connectivity is lost, what do you mean specifically? e.g. if you use netcat/telnet to try and communicate with running containers, do you: (a) get an immediate connection refused failure; or (b) manage to open a connection, but one that is essentially 'hung' (no data actually reaches the container) I'm trying to determine whether or not to raise a new issue here in relation to: - testcontainers/testcontainers-java#1623 <testcontainers/testcontainers-java#1623> - https://forums.docker.com/t/port-forward-not-working-on-a-macos-installation-but-works-on-others/77401 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3647?email_source=notifications&email_token=AAYMHXKU4ZU3PL4NN6VNGIDQABH4VA5CNFSM4HJRWAUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2IF56A#issuecomment-512777976>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAYMHXIRLICCAFO5TYKE5TTQABH4VANCNFSM4HJRWAUA> .

[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

[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