summaryrefslogtreecommitdiff
path: root/troubleshooting.md
diff options
context:
space:
mode:
authorPaul Holzinger <paul.holzinger@web.de>2020-12-11 17:02:21 +0100
committerPaul Holzinger <paul.holzinger@web.de>2020-12-11 23:15:09 +0100
commit74fcd9fef3a31fa94f3487361b5fda1180e8cee2 (patch)
treec169ef67233ca8d31d14c947ab4c09cea5189619 /troubleshooting.md
parentdd954781e6e308a0bbecfaf6699b41426100a58d (diff)
downloadpodman-74fcd9fef3a31fa94f3487361b5fda1180e8cee2.tar.gz
podman-74fcd9fef3a31fa94f3487361b5fda1180e8cee2.tar.bz2
podman-74fcd9fef3a31fa94f3487361b5fda1180e8cee2.zip
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>
Diffstat (limited to 'troubleshooting.md')
0 files changed, 0 insertions, 0 deletions