Stan Lagun 0549313491 [Docker] Do not try to delete container on destroyed host ...

When Environment get deleted both Docker/k8s host and
Docker applications get deleted. So it is possible that host
will try to delete container from an Instance that was already
destroyed. Attempt to send commands to such instance
will hang until timeout because there is no more agent
exist on the other side.

Change-Id: Ia6e8064ae50c24ce595ed08e446ed45b96b4a330
Closes-Bug: #1504623
Depends-On: I298f3f079a153ef87ed7213b7f1432c9e5e4b4b6

2015-10-12 11:23:27 +00:00

Applications

Requirements were incorrect for many apps

2015-09-02 21:21:58 +03:00

DockerInterfacesLibrary/package

[Docker] Do not try to delete container on destroyed host

2015-10-12 11:23:27 +00:00

DockerStandaloneHost

[Docker] Do not try to delete container on destroyed host

2015-10-12 11:23:27 +00:00

Kubernetes

[Docker] Do not try to delete container on destroyed host

2015-10-12 11:23:27 +00:00

Description

Suite of the Docker and Kubernetes applications

1.8 MiB

Languages

Shell 54.7%

Python 44.9%

reStructuredText 0.4%