Files
Matthew Heon 9dcd76e369 Ensure we generate a 'stopped' event on force-remove
When forcibly removing a container, we are initiating an explicit
stop of the container, which is not reflected in 'podman events'.
Swap to using our standard 'stop()' function instead of a custom
one for force-remove, and move the event into the internal stop
function (so internal calls also register it).

This does add one more database save() to `podman remove`. This
should not be a terribly serious performance hit, and does have
the desirable side effect of making things generally safer.

Signed-off-by: Matthew Heon <matthew.heon@pm.me>
2019-07-31 17:29:14 -04:00
..
2019-06-03 15:54:53 -04:00
2017-11-01 11:24:59 -04:00
2019-07-03 15:41:33 -05:00
2019-07-11 09:13:06 -05:00
2019-01-18 15:43:11 -06:00
2019-07-08 09:18:11 -05:00
2019-07-11 09:13:06 -05:00
2019-07-22 15:44:04 -05:00
2019-07-21 14:22:39 -05:00
2019-07-07 08:54:20 -05:00
2019-07-22 15:57:23 -04:00
2019-06-25 13:51:24 -05:00
2019-06-27 07:56:24 -05:00
2019-07-21 14:22:39 -05:00
2019-07-22 15:57:23 -04:00
2019-07-23 10:13:04 -05:00
2019-07-23 10:13:04 -05:00
2019-07-22 15:57:23 -04:00
2019-07-22 15:57:23 -04:00
2019-07-22 15:57:23 -04:00
2019-06-27 07:56:24 -05:00
2019-06-25 13:51:24 -05:00
2019-06-25 13:51:24 -05:00
2019-06-25 13:51:24 -05:00
2019-06-25 13:51:24 -05:00
2019-06-25 13:51:24 -05:00
2019-07-08 09:18:11 -05:00
2019-07-21 14:22:39 -05:00
2019-06-25 13:51:24 -05:00
2019-06-25 13:51:24 -05:00
2019-07-30 12:25:36 -04:00
2019-06-25 13:51:24 -05:00
2018-03-14 20:21:31 +00:00
2019-06-25 13:51:24 -05:00
2019-07-08 09:18:11 -05:00
2019-02-21 10:51:42 -05:00