Restart network container when container's configure is changed.

Fix #2099

I could improve this by figuring out if the network related configuration is changed, then decided if restart network container or not. But thought the user expects a blackout time during configuration update anyway.  
Won't this kill the network container multiple times?