eae1b7d6bd
When cri-o assumes the container creation failed, we need to let the runtime know that we're bailing out so that it cancels all ongoing operation. In container creation timeout situations for example, failing to explictly request the runtime for container deletion can lead to large resource leaks as kubelet re-creates a failing container, while the runtime finishes creating the previous one(s). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> |
||
|---|---|---|
| .. | ||
| container.go | ||
| finished.go | ||
| finished_32.go | ||
| history.go | ||
| memory_store.go | ||
| oci.go | ||
| store.go | ||