Description of problem:

All Podman events functionality is nonfunctional using the default configuration as shipped in RHEL 8.3.1

Version-Release number of selected component (if applicable):

Podman v2.1.1 as will be shipped in RHEL 8.3.1

How reproducible:

100%

Steps to Reproduce:
0. Ensure you are logged in as a non-root user who is *not* part of the wheel group.
1. `podman run -t -i --name test fedora ls` in one terminal
2. `podman rm --force test` in a second terminal

(The `podman events` command is another good example)

Actual results:

The command returns an error that we were unable to retrieve the error code

Expected results:

Command succeeds and correctly returns error code

Additional info:

The default for events prior to v2.1.1 was `file`, which does not have this issue. In v2.1.1, we swapped the default to `journald` backend to resolve some issues with the `file` backend (it could fill up `/run` on systems generating a lot of events). Unfortunately, on RHEL 8.x, it appears that non-root users that are not in the wheel group cannot access the journal; this was not caught elsewhere because other distributions ship a more modern systemd that does not have this issue.

We have contacted the systemd team and are inquiring about further details, but any potential backports and fixes there can wait until 8.4.0. For now, we can swap the default back in Podman via a configuration file change to resolve the issue.