I noticed this while experimenting with etcd container restart. Just filing it to discuss if this needs to be resolved in netplugin in anyway. I feel it might be desirable to handle this a bit more gracefully by retrying the connection and failing subsequent client requests.
Right now the system get's into a weird state with this behavior. Basically once docker is stopped, etcd container stops and netplugin panics. From this point on restarting docker doesn't work as it seems to be waiting on netplugin (which looks like docker bug but I couldn't find any known issues). Netplugin won't start as it needs etcd. And etcd won't start as it needs docker :)
Docker version:
[vagrant@host0 ~]$ sudo docker version
Client:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Wed Apr 27 00:34:42 2016
OS/Arch: linux/amd64
Server:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Wed Apr 27 00:34:42 2016
OS/Arch: linux/amd64
I noticed this while experimenting with etcd container restart. Just filing it to discuss if this needs to be resolved in netplugin in anyway. I feel it might be desirable to handle this a bit more gracefully by retrying the connection and failing subsequent client requests.
Right now the system get's into a weird state with this behavior. Basically once docker is stopped, etcd container stops and netplugin panics. From this point on restarting docker doesn't work as it seems to be waiting on netplugin (which looks like docker bug but I couldn't find any known issues). Netplugin won't start as it needs etcd. And etcd won't start as it needs docker :)
Docker version:
Netplugin Version:
Docker logs showing that it is waiting on netplugin:
Netplugin logs showing panic backtrace: