Containers leaky as a vegetable #1669
Description
Containers are not cleaned up, leading to increasingly more containers running over time, leading to eventual subnet exhaustion (not directly experienced yet in this phase of testing, but it'll clearly happen).
Kubernetes 1.7.0, Ubuntu 16.04.3 LTS, non-default kernel 4.10.0-28-generic.
This is basically a refiling of #1424, but against Concourse 3.5.0. I'm raising a new ticket since related #1297 and #1413 have been closed and released, yet the problem persists.
{"timestamp":"1506512429.404951572","source":"guardian","message":"guardian.destroy.destroy.delete-failed","log_level":2,"data":{"error":"runc create: exit status 1: container init still running\n","handle":"dcea3bf8-93b5-4e42-5c9d-a69db690604e","session":"3613.1"}}
{"timestamp":"1506512429.405071259","source":"guardian","message":"guardian.api.garden-server.destroy.failed","log_level":2,"data":{"error":"runc create: exit status 1: container init still running\n","handle":"dcea3bf8-93b5-4e42-5c9d-a69db690604e","session":"3.1.4513"}}