Spurious route removal

[SpComb]

Docker connect network event is causing the network route to be removed.

2016/08/12 11:14:22 docker:Docker.Open: docker.Client unix:///var/run/docker.sock
2016/08/12 11:14:22 docker:Containers.list 64f1d22773b5990e53b6810f7da8ab5f03b57e1ec12904163eec9ce90aecb644: up
2016/08/12 11:14:22 docker:Containers.list 6a8781b42969dc1cf4c2315d55ac5264b9e89887cc08362a45a259364090dd48: down
2016/08/12 11:14:22 docker:Networks.list f185b865358d5623c07d2a69cd4f29b64b3fce69a7c699b253150d27da126c9d: up
2016/08/12 11:14:22 docker:Networks.list 147eff011b25ca05846331d1ba58f6c93770cd41edb830dea535f8f008659ee0: up
2016/08/12 11:14:22 docker:Networks.list 0b17207c64618c5690948aa423642474b5542d76bd3bba7389628e9f400bae72: up
2016/08/12 11:14:22 docker:Docker.Listen...
2016/08/12 11:14:22 Update config...
2016/08/12 11:14:22 config:EtcdSource etcd+http://127.0.0.1:2379/clusterf: writer: new routes/147eff011b25ca05846331d1ba58f6c93770cd41edb830d
2016/08/12 11:14:22 config:EtcdSource etcd+http://127.0.0.1:2379/clusterf: writer: update in 102.519388ms
2016/08/12 11:16:52 config:EtcdSource etcd+http://127.0.0.1:2379/clusterf: refresh after 102.519388ms+2m29.897755722s
2016/08/12 11:17:00 docker:Client.updateState: pull image registry.docker.catcp/iperf:latest: skip
2016/08/12 11:17:00 Update config...
2016/08/12 11:17:00 config:EtcdSource etcd+http://127.0.0.1:2379/clusterf: writer: update in 3.379µs
2016/08/12 11:18:06 docker:Containers.update create container 2de6ab3971ee3e6d51b6ecc303999137ca7819fd8ce57f312d5dc170ae5dc158 -> created: up
2016/08/12 11:18:06 Update config...
2016/08/12 11:18:06 config:EtcdSource etcd+http://127.0.0.1:2379/clusterf: writer: update in 2.671µs
2016/08/12 11:18:06 docker:Containers.update attach container 2de6ab3971ee3e6d51b6ecc303999137ca7819fd8ce57f312d5dc170ae5dc158 -> created: up
2016/08/12 11:18:06 Update config...
2016/08/12 11:18:06 config:EtcdSource etcd+http://127.0.0.1:2379/clusterf: writer: update in 2.558µs
2016/08/12 11:18:06 docker:Networks.update connect network 147eff011b25ca05846331d1ba58f6c93770cd41edb830dea535f8f008659ee0 -> {false}: remove
2016/08/12 11:18:06 Update config...
2016/08/12 11:18:06 config:EtcdSource etcd+http://127.0.0.1:2379/clusterf: writer: remove routes/147eff011b25ca05846331d1ba58f6c93770cd41edb830dea535f8f008659ee0
2016/08/12 11:18:06 config:EtcdSource etcd+http://127.0.0.1:2379/clusterf: writer: update in 49.817773ms
2016/08/12 11:18:07 docker:Containers.update start container 2de6ab3971ee3e6d51b6ecc303999137ca7819fd8ce57f312d5dc170ae5dc158 -> running: down
2016/08/12 11:18:07 Update config...
2016/08/12 11:18:07 config:EtcdSource etcd+http://127.0.0.1:2379/clusterf: writer: new services/iperf/backends/2de6ab3971ee3e6d51b6ecc303999137ca7819fd8ce57f312d5dc170ae5dc158
2016/08/12 11:18:07 config:EtcdSource etcd+http://127.0.0.1:2379/clusterf: writer: update in 27.127355ms

[SpComb]

Fixed in 23a9d0b. All Docker networkEvents were broken, but I suppose earlier docker+docker-compose versions didn't trigger network connect events..