| Commit message (Collapse) | Author | Age | ||
|---|---|---|---|---|
| ... | ||||
| * | | Add locking to ensure events file is concurrency-safe | Matthew Heon | 2019-03-29 | |
| |/ | | | | Signed-off-by: Matthew Heon <matthew.heon@pm.me> | |||
| * | Add "died" event | baude | 2019-03-25 | |
| | | | | | | | | | | | 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> | |||
| * | Add event on container death | Matthew Heon | 2019-03-13 | |
| | | | | | Signed-off-by: Matthew Heon <matthew.heon@pm.me> | |||
| * | Add event logging to libpod, even display to podman | baude | 2019-03-11 | |
| 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> | ||||
 |
index : containers/podman.git | |
| forked from: https://github.com/containers/podman.git | User & |
| summaryrefslogtreecommitdiff |