[3402663907] Upstream Reporter: Jindrich Novy
Upstream issue status: Closed
Upstream description:

https://github.com/containers/podman/issues/27038 describes a problem where systemd priority prefixes like <7> in application output are not properly parsed when using LogDriver=journald. Instead of being converted to proper journal priority levels, they appear literally in log messages.

The current conmon journald logging implementation:

1. Hard-codes priority levels:

• PRIORITY=6 for stdout (line 329)
• PRIORITY=3 for stderr (line 331)

1. Raw data pass-through: In read_stdio() (src/ctr_stdio.c:149), container output is passed directly to write_to_logs() without any preprocessing or parsing of systemd priority prefixes.
2. No priority prefix parsing: The code does not check for or strip systemd priority prefixes like <0>, <1>, <7>, etc. from the beginning of log lines.