podman logs -f fails with Error: using --follow with the journald --log-driver but without the journald --events-backend (file) is not supported on opensuse leap 15.4

[fuomag9]

Issue Description

I get the error Error: using --follow with the journald --log-driver but without the journald --events-backend (file) is not supported when doing podman logs -f {containedid}

Steps to reproduce the issue

Steps to reproduce the issue

1. Install opensuse leap 15.4
2. Install podman
3. Run a container
4. Try to get the logs via podman logs -f {containedid}

Describe the results you received

Error: using --follow with the journald --log-driver but without the journald --events-backend (file) is not supported

Describe the results you expected

The logs

podman info output

host:
  arch: amd64
  buildahVersion: 1.29.0
  cgroupControllers: []
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: conmon-2.1.5-150400.3.8.1.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.5, commit: unknown'
  cpuUtilization:
    idlePercent: 67.37
    systemPercent: 2.55
    userPercent: 30.07
  cpus: 2
  distribution:
    distribution: '"opensuse-leap"'
    version: "15.4"
  eventLogger: file
  hostname: nine-eleven
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 100
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.14.21-150400.24.63-default
  linkmode: dynamic
  logDriver: journald
  memFree: 123572224
  memTotal: 2480283648
  networkBackend: cni
  ociRuntime:
    name: runc
    package: runc-1.1.5-150000.43.1.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.1.5
      commit: v1.1.5-0-gf19387a6bec4
      spec: 1.0.2-dev
      go: go1.19.9
      libseccomp: 2.5.3
  os: linux
  remoteSocket:
    exists: true
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /etc/containers/seccomp.json
    selinuxEnabled: false
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.2.0-150300.8.5.2.x86_64
    version: |-
      slirp4netns version 1.2.0
      commit: unknown
      libslirp: 4.7.0
      SLIRP_CONFIG_VERSION_MAX: 5
      libseccomp: 2.5.3
  swapFree: 1268625408
  swapTotal: 1341104128
  uptime: 0h 44m 22.00s
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - registry.opensuse.org
  - registry.suse.com
  - docker.io
store:
  configFile: /home/fuomag9/.config/containers/storage.conf
  containerStore:
    number: 1
    paused: 0
    running: 1
    stopped: 0
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/fuomag9/.local/share/containers/storage
  graphRootAllocated: 19595788288
  graphRootUsed: 4189528064
  graphStatus:
    Backing Filesystem: btrfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 1
  runRoot: /run/user/1000/containers
  transientStore: false
  volumePath: /home/fuomag9/.local/share/containers/storage/volumes
version:
  APIVersion: 4.4.4
  Built: 1680004800
  BuiltTime: Tue Mar 28 14:00:00 2023
  GitCommit: ""
  GoVersion: go1.18.10
  Os: linux
  OsArch: linux/amd64
  Version: 4.4.4

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

No

Additional environment details

No response

Additional information

No response

[Luap99]

As the error says this is not supported you have to change your event logger to journald or the container logger to k8s-file. You can set this in containers.conf, see log_driver and events_logger.

If your distro ships with non working defaults you should report this to the packager.

[fsdrw08]

reboot the host should be resolve this problem