cri-o/oci
Daniel J Walsh d679da0645 If the container exit file is missing default exit code to -1
If I create a sandbox pod and then restart the ocid service, the
pod ends up in a stopped state without an exit file.  Whether this is
a bug in ocid or not we should handle this case where a container exits
so that we can clean up the container.

This change just defaults to exit code to -1 if the container is not
running and does not have an exit file.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2017-03-21 08:00:04 -04:00
..
history.go use an in memory store for containers 2016-09-19 13:11:36 +02:00
memory_store.go fix typo to make go report more happy 2017-01-04 14:24:11 +08:00
oci.go If the container exit file is missing default exit code to -1 2017-03-21 08:00:04 -04:00
store.go use an in memory store for containers 2016-09-19 13:11:36 +02:00