11 Commits (bb7cc740694368c673c7790a19c8f0e9e2899ce6)

Author	SHA1	Message	Date
Dan Williams	4d7d7faa81	dockertools: clean up networking when garbage-collecting pods ... The docker runtime doesn't tear down networking when GC-ing pods. rkt already does so make docker do it too. To ensure this happens, networking is always torn down for the container even if the container itself is not deleted. This prevents IPAM from leaking when the pod gets killed for some reason outside kubelet (like docker restart) or when pods are killed while kubelet isn't running. Fixes: https://github.com/kubernetes/kubernetes/issues/14940 Related: https://github.com/kubernetes/kubernetes/pull/35572	2017-02-16 13:51:19 -06:00
deads2k	6a4d5cd7cc	start the apimachinery repo	2017-01-11 09:09:48 -05:00
Yu-Ju Hong	03971d3992	dockershim: implement ContainerStatus()	2016-07-28 18:24:29 -07:00
Ron Lai	0a651402f2	- Added a DeleteContainer method in Runtime interface ... - Implemented DeleteContainer for docker	2016-07-08 10:40:30 -07:00
David McMahon	ef0c9f0c5b	Remove "All rights reserved" from all the headers.	2016-06-29 17:47:36 -07:00
Yu-Ju Hong	f279e36292	Don't remove all containers of deleted pods until sources are ready ... Without this fix, kubelet may assume a pod from a not-ready source has already been deleted, and GC all its dead containers.	2016-06-16 10:47:12 -07:00
Random-Liu	d3d98b372b	Refactor StartContainer, StopContainer and RemoveContainer.	2016-04-14 17:05:46 -07:00
Random-Liu	da07fa9dd5	Refactor InspectContainer.	2016-04-14 17:05:46 -07:00
Tim St. Clair	3ad59de829	Garbage collect containers for deleted pods	2016-03-02 14:35:17 -08:00
feisky	d624c7de51	Pass the ContainerGCPolicy in Runtime.GarbageCollect	2015-10-09 06:57:10 +08:00
feisky	4c8a836260	Move original container gc to docker runtime	2015-10-09 06:57:09 +08:00