podman

Author	SHA1	Message	Date
OpenShift Merge Robot	e435931544	Merge pull request #2801 from mheon/remove_wait_event Remove wait event	2019-03-29 15:10:04 -07:00
Matthew Heon	99318b0894	Remove wait event It's not necessary to log an event for a read-only operation like wait. Signed-off-by: Matthew Heon <matthew.heon@pm.me>	2019-03-29 14:50:43 -04:00
Matthew Heon	8108801247	Add locking to ensure events file is concurrency-safe Signed-off-by: Matthew Heon <matthew.heon@pm.me>	2019-03-29 12:51:37 -04:00
baude	e730fc6093	Add "died" event We have a new event for container 'Exited' which has been renamed to 'died'. also removed the stream bool from the varlink endpoint for events because it can be determined by the varlink more value. Signed-off-by: baude <bbaude@redhat.com>	2019-03-25 10:28:50 -05:00
Matthew Heon	3b5805d521	Add event on container death Signed-off-by: Matthew Heon <matthew.heon@pm.me>	2019-03-13 10:18:51 -04:00
baude	ca1e76ff63	Add event logging to libpod, even display to podman In lipod, we now log major events that occurr. These events can be displayed using the `podman events` command. Each event contains: * Type (container, image, volume, pod...) * Status (create, rm, stop, kill, ....) * Timestamp in RFC3339Nano format * Name (if applicable) * Image (if applicable) The format of the event and the varlink endpoint are to not be considered stable until cockpit has done its enablement. Signed-off-by: baude <bbaude@redhat.com>	2019-03-11 15:08:59 -05:00