Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-3161

Logger does not capture data of a container after a container restart

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • rhel-9.2.0
    • podman-container
    • Normal
    • sst_container_tools
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • If docs needed, set a value
    • 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.

            mheon@redhat.com Matt Heon
            rhn-support-cpippin Carroline Pippin
            Matt Heon Matt Heon
            Container QE Container QE Container QE Container QE
            Gabriela Necasova Gabriela Necasova
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: