docker 17.06 keeps restarting on n/w status change

[kvahuja]

Expected behavior

It should keep running and not restart when i turn off my network

Actual behavior

when I connect or DC my WIFI, docker engine resarts

Steps to reproduce the behavior

1. Start Docker
2. Turn off WIFI
3. Docker Restarts
4. Once Docker is running, turn on WIFI - it restart again

There is a bug in docker-compose where I can't run the command as it hangs when I am connected to a n/w. So this pretty much means, Docker is useless for me.

how do i run docker-compose while connected to the n/w?? or why is docker restarting all the time. I could earlier just clos emy MAC and bring it back-up and everythign was running. now i have to restart everything all the time,

is this a Bug? i hope this is a bug?

[siosphere]

Same here with latest update:

Docker version 17.06.0-ce, build 02c1d87

OSX El Capitan 10.11.6

[tanmng]

I'm experiencing the same issue

Below is my docker info

><((°> docker info                                                                                                                            22:49:11
Containers: 9
 Running: 1
 Paused: 0
 Stopped: 8
Images: 131
Server Version: 17.06.0-ce
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 178
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfb82a876ecc11b5ca0977d1733adbe58599088a
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.31-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.855GiB
Name: moby
ID: XYVQ:L2GE:4Y7K:BIJP:SY7S:YBEO:YBB7:BV3J:JP23:YJCI:IJ2V:JLWE
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 25
 Goroutines: 35
 System Time: 2017-06-30T19:50:11.099137705Z
 EventsListeners: 1
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

[siosphere]

Duplicate of #1789

[djs55]

Please upload diagnostics (from the Whale menu -> Diagnose and Feedback ...). Without the uploaded logs it will be hard to correctly diagnose the issue.

[tanmng]

@djs55 After some restarts, Docker for Mac now appears to be stable again and I don't experience the issue any longer

Is it still necessary to upload my diagnostics?

[djs55]

@tanmng if it's stabilised don't worry about it. FYI there should be a 17.06.1 with some fixes in this area this week. Let me know if you have any further problems!

[gow]

Still happening with me. Here is my diagnostic ID: 5795AC98-CB11-4D02-B390-2F894381D185
Build:
Version 17.06.0-ce-mac18 (18433)
Channel: stable
d9b66511e0

[zambotn]

Same problem here!
6B5763CA-409E-4B0F-8A85-B0D251744997

Docker for Mac: version: 17.06.0-ce-mac18 (4cdec4294a50b2233146b09469b49937dabdebdd)
macOS: version 10.12.5 (build: 16F73)

[coladarci]

Same here...
C2C5057A-146F-4E2B-B29B-51786494B6B9

Version 17.06.0-ce-mac18 (18433)
Channel: stable
d9b66511e0

What's the easiest way to downgrade? This is starting to become a big problem for us..

[djs55]

The fix for this should be in the latest stable patch:

Version 17.06.0-ce-mac19 (18663)
Channel: stable
c98c1c25e0

If there are still problems, could you upload a fresh diagnostic and let me know?

Thanks for your reports.

[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