Jana Radhakrishnan 34120dcd16 Do not attempt releasing network when not attached to any network ...

Sometimes container.cleanup() can be called from multiple paths
for the same container during error conditions from monitor and
regular startup path. So if the container network has been already
released do not try to release it again.

Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>
Upstream-commit: 6cdf8623d52e7e4c5b5265deb5f5b1d33f2e6e95
Component: engine

2015-05-21 18:57:17 +00:00

components/engine

Do not attempt releasing network when not attached to any network

2015-05-21 18:57:17 +00:00

Description

No description provided

310 MiB

Languages

Go 92%

Shell 5.5%

Dockerfile 1.1%

Go-Checksums 0.9%

Makefile 0.3%

Other 0.2%