Podman-rootless containers and systemd journal: default log driver decision

Determine whether Podman should enable journald logging by default for rootless containers to improve integration with the systemd journal.

Rootless containers run without elevated privileges, which may prevent them from writing to the system journal; relying on a manual --log-driver=journald flag can lead to inconsistent logging, while preserving the existing file‑based log path is important for users who depend on podman logs output. Any change must also consider log rotation, storage impact, and permission safeguards.

Should Podman automatically detect a running systemd user session and switch the log driver to journald for rootless containers? What safeguards are needed to avoid permission failures or journal overload? How would this change affect existing workflows that rely on podman logs output?