You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With "Use system proxy" option enabled if you loose internet connectivity by detaching the ethernet cable or shutting down the wifi, the docker daemon restarts itself. The same behavior occurs when you attach back the ethernet cable.
Information
I don't have any system wide proxy configured ("Use system proxy" is the default option). If i switch to "No proxy" the daemon does not restarts anymore.
Full output of the diagnostics from "Diagnose & Feedback" in the menu
A reproducible case if this is a bug, Dockerfiles FTW
Page URL if this is a docs issue or the name of a man page
Steps to reproduce the behavior
Activate "Use system proxy option" under Proxy preferences
Thanks for your report. I think this is the same issue as #1809. There's a fix scheduled to be released in 17.06.1 which is due to be released very soon. I'm sorry for the inconvenience in the meantime.
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
Expected behavior
Docker daemon does NOT restarts
Actual behavior
With "Use system proxy" option enabled if you loose internet connectivity by detaching the ethernet cable or shutting down the wifi, the docker daemon restarts itself. The same behavior occurs when you attach back the ethernet cable.
Information
I don't have any system wide proxy configured ("Use system proxy" is the default option). If i switch to "No proxy" the daemon does not restarts anymore.
Steps to reproduce the behavior
DIagnostic ID: E3C8F3A8-6D09-4A7C-984B-9D4D05A933DB
The text was updated successfully, but these errors were encountered: