Woodpecker agent fails to see finish on podman user socket if journald is set to MaxLevelStore=warning

[waffshappen]

Component

agent

Describe the bug

When running woodpecker agent as follows:

podman run -d --security-opt="label=disable" --tmpfs /tmp --cgroups=split --restart=no --label io.containers.autoupdate=registry --hostname woodpeckeragent --name woodpeckeragent --tz Europe/Berlin -e DOCKER_HOST="unix:///run/user/1001/podman/podman.sock" -e WOODPECKER_SERVER=[..] -e WOODPECKER_AGENT_SECRET=[..] -e WOODPECKER_MAX_PROCS=2 -e WOODPECKER_KEEPALIVE_TIME=60s -v /run/user/1001/podman/podman.sock:/run/user/1001/podman/podman.sock --cpu-shares=128 --memory=2G docker.io/woodpeckerci/woodpecker-agent:latest

And with (this doesnt change the result, was an attempt)

~/.config/containers/containers.conf 
[containers]
log_driver="json-file"

And

/etc/systemd/journald.conf.d/10-journald.conf
MaxLevelStore=warning

woodpecker agent never realizes when a container is finished and will be stuck waiting forever.

If MaxLevelStore is set to default it will work immediately.

System Info

{"source":"https://github.com/woodpecker-ci/woodpecker","version":"1.0.0-rc1"}

Fedora 38, podman with podman-docker and podman user socket enabled & passed through. :latest agent (v1.0.0-rc1, https://hub.docker.com/layers/woodpeckerci/woodpecker-agent/v1.0.0-rc1/images/sha256-aec2f68b57381d2dcf5176c8b6f6349c8dfacf6c0090d2db932917a36e391875?context=explore ) .

Additional context

No response

Validations

• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
• [X] Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

[waffshappen]

Issue still occurs in 1.0.1

[waffshappen]

Config Change Required is in linked report