podman/libpod/events
Matt Heon be3f075402 Make `podman update` changes persistent
The logic here is more complex than I would like, largely due to
the behavior of `podman inspect` for running containers. When a
container is running, `podman inspect` will source as much as
possible from the OCI spec used to run that container, to grab
up-to-date information on things like devices. We don't want to
change this, it's definitely the right behavior, but it does make
updating a running container inconvenient: we have to rewrite the
OCI spec as part of the update to make sure that `podman inspect`
will read the correct resource limits.

Also, make update emit events. Docker does it, we should as well.

Signed-off-by: Matt Heon <mheon@redhat.com>
2024-04-17 08:23:50 -04:00
..
config.go Make `podman update` changes persistent 2024-04-17 08:23:50 -04:00
events.go Make `podman update` changes persistent 2024-04-17 08:23:50 -04:00
events_freebsd.go events: Fix spelling of newNullEventer 2022-09-13 08:38:13 +01:00
events_linux.go event backend none: return an error when reading events 2022-09-12 18:05:17 +02:00
events_unsupported.go chore: delete obsolete // +build lines 2024-01-04 11:53:38 +02:00
filters.go Bump Go module to v5 2024-02-08 09:35:39 -05:00
journal_linux.go properly implement pull-error event status 2024-03-05 10:50:42 +01:00
journal_unsupported.go chore: delete obsolete // +build lines 2024-01-04 11:53:38 +02:00
logfile.go Bump Go module to v5 2024-02-08 09:35:39 -05:00
logfile_test.go events: no duplicates when streaming during a log rotation 2023-03-15 10:28:16 +01:00
memory.go Add podman machine events 2022-05-03 13:49:01 -07:00
nullout.go Fix typos. Improve language. 2023-02-09 21:56:27 +01:00