Jana Radhakrishnan 117cef5e97 Retry creating dynamic networks if not found ... In cases there are failures in task start, swarmkit might be trying to restart the task again in the same node which might keep failing. This creates a race where when a failed task is getting removed it might remove the associated network while another task for the same service or a different service but connected to the same network is proceeding with starting the container knowing that the network is still present. Fix this by reacting to `ErrNoSuchNetwork` error during container start by trying to recreate the managed networks. If they have been removed it will be recreated. If they are already present nothing bad will happen. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>		2016-08-09 13:37:11 -07:00
..
container	Retry creating dynamic networks if not found	2016-08-09 13:37:11 -07:00
backend.go	improve error message when using ineligible network with service create	2016-07-25 08:31:22 -07:00