podman/libpod/events
Paul Holzinger 74fcd9fef3 podman events allow future time for --until
The podman events aren't read until the given timestamp if the
timestamp is in the future. It just reads all events until now
and exits afterwards.
This does not make sense and does not match docker. The correct
behavior is to read all events until the given time is reached.

This fixes a bug where the wrong event log file path was used
when running first time with a new storage location.
Fixes #8694

This also fixes the events api endpoint which only exited when
an error occurred. Otherwise it just hung after reading all events.

Signed-off-by: Paul Holzinger <paul.holzinger@web.de>
2020-12-11 23:15:09 +01:00
..
config.go rewrite podman-cp 2020-12-04 14:39:55 +01:00
events.go podman events allow future time for --until 2020-12-11 23:15:09 +01:00
events_linux.go Remove all instances of named return "err" from Libpod 2020-07-09 13:54:47 -04:00
events_unsupported.go journald event logging 2019-04-24 16:00:04 -05:00
filters.go filter events by labels 2020-10-23 12:07:34 -05:00
journal_linux.go podman events allow future time for --until 2020-12-11 23:15:09 +01:00
journal_unsupported.go set default event logger based on build tags 2019-05-14 16:17:11 -05:00
logfile.go podman events allow future time for --until 2020-12-11 23:15:09 +01:00
nullout.go Fix `system service` panic from early hangup in events 2020-07-02 09:57:39 -04:00