-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
rhel-9.2.0
-
None
-
Moderate
-
rhel-sst-container-tools
-
None
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
x86_64
-
None
Description of problem:
`logger test` from inside the container does not output the message after the container restarts
Version-Release number of selected component (if applicable):
RHEL 9.2
Podman
How reproducible:
Steps to Reproduce:
1. podman run -d --cap-add ALL --name logger registry.redhat.io/rhel9/rsyslog:latest
2. podman exec -it logger /bin/bash
3. Inside the Container : $ logger test
4. Outside the container: $ podman inspect --format='.HostConfig.LogConfig.Path' <container-id>
5. [root@rhel88 ~]# tail -f /var/lib/containers/storage/overlay-containers/4e1ceed92a9eaa8bb09196e825e1e1cbf4b1b8f6d60a6285c05d1532fb700ab9/userdata/ctr.log
[root@4e1ceed92a9e /]#
2023-08-16T11:48:02.799138055+05:30 stdout P logger test
6. Stop and start the container and perform the same steps to capture logger output it does not log the message.
Actual results:
Logger does not log messages after a container restart
Expected results:
Logger should log messages always.
Additional info:
$ podman logs <container_id> does not log message after the restart as well.
- is duplicated by
-
RHEL-3160 Logger does not capture data of a container after a container restart
- Closed
- external trackers