18.6. Monitoring Podman events

Procedure

1. Run the myubi container:

   $ podman run -q --rm --name=myubi registry.access.redhat.com/ubi10/ubi:latest

2. Display the Podman events:

   • To display all Podman events, enter:

     $ now=$(date --iso-8601=seconds)
     $ podman events --since=now --stream=false
     2023-03-08 14:27:20.696167362 +0100 CET container create d4748226a2bcd271b1bc4b9f88b54e8271c13ffea9b30529968291c62d72fe09 (image=registry.access.redhat.com/ubi10/ubi:latest, name=myubi,...)
     2023-03-08 14:27:20.652325082 +0100 CET image pull  registry.access.redhat.com/ubi10/ubi:latest
     2023-03-08 14:27:20.795695396 +0100 CET container init d4748226a2bcd271b1bc4b9f88b54e8271c13ffea9b30529968291c62d72fe09 (image=registry.access.redhat.com/ubi10/ubi:latest, name=myubi...)
     2023-03-08 14:27:20.809205161 +0100 CET container start d4748226a2bcd271b1bc4b9f88b54e8271c13ffea9b30529968291c62d72fe09 (image=registry.access.redhat.com/ubi10/ubi:latest, name=myubi...)
     2023-03-08 14:27:20.809903022 +0100 CET container attach d4748226a2bcd271b1bc4b9f88b54e8271c13ffea9b30529968291c62d72fe09 (image=registry.access.redhat.com/ubi10/ubi:latest, name=myubi...)
     2023-03-08 14:27:20.831710446 +0100 CET container died d4748226a2bcd271b1bc4b9f88b54e8271c13ffea9b30529968291c62d72fe09 (image=registry.access.redhat.com/ubi10/ubi:latest, name=myubi...)
     2023-03-08 14:27:20.913786892 +0100 CET container remove d4748226a2bcd271b1bc4b9f88b54e8271c13ffea9b30529968291c62d72fe09 (image=registry.access.redhat.com/ubi10/ubi:latest, name=myubi...)

     The --stream=false option ensures that the podman events command exits when reading the last known event.

     You can see several events that happened when you enter the podman run command:

     • container create when creating a new container.
     • image pull when pulling an image if the container image is not present in the local storage.
     • container init when initializing the container in the runtime and setting a network.
     • container start when starting the container.
     • container attach when attaching to the terminal of a container. That is because the container runs in the foreground.
     • container died is emitted when the container exits.
     • container remove because the --rm flag was used to remove the container after it exits.

   • You can also use the journalctl command to display Podman events:

     $ journalctl --user -r SYSLOG_IDENTIFIER=podman
     Mar 08 14:27:20 fedora podman[129324]: 2023-03-08 14:27:20.913786892 +0100 CET m=+0.066920979 container remove
     ...
     Mar 08 14:27:20 fedora podman[129289]: 2023-03-08 14:27:20.696167362 +0100 CET m=+0.079089208 container create d4748226a2bcd271b1bc4b9f88b54e8271c13ffea9b30529968291c62d72f>

   • To show only Podman create events, enter:

     $ podman events --filter event=create
     2023-03-08 14:27:20.696167362 +0100 CET container create d4748226a2bcd271b1bc4b9f88b54e8271c13ffea9b30529968291c62d72fe09 (image=registry.access.redhat.com/ubi10/ubi:latest, name=myubi,...)

   • You can also use the journalctl command to display Podman create events:

     $ journalctl --user -r PODMAN_EVENT=create
     Mar 08 14:27:20 fedora podman[129289]: 2023-03-08 14:27:20.696167362 +0100 CET m=+0.079089208 container create d4748226a2bcd271b1bc4b9f88b54e8271c13ffea9b30529968291c62d72f>

     For more information, see the podman-events(1) man page on your system.