Warning message `WARN[0000] The cgroupv2 manager is set to systemd but ...` is printed twice

Issue Description

This warning message is printed twice

WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
WARN[0000] For using systemd, you may need to log in using a user session 
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1008` (possibly as root) 
WARN[0000] Falling back to --cgroup-manager=cgroupfs   

the second time running sudo -iu test podman ps

Steps to reproduce the issue

Steps to reproduce the issue

1. Create user

   $ sudo useradd test
   

2. Run command

   $ sudo -iu test podman ps
   WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
   WARN[0000] For using systemd, you may need to log in using a user session 
   WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1008` (possibly as root) 
   WARN[0000] Falling back to --cgroup-manager=cgroupfs    
   CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES
   

3. Run the same command again

   $ sudo -iu test podman ps
   WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
   WARN[0000] For using systemd, you may need to log in using a user session 
   WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1008` (possibly as root) 
   WARN[0000] Falling back to --cgroup-manager=cgroupfs    
   WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
   WARN[0000] For using systemd, you may need to log in using a user session 
   WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1008` (possibly as root) 
   WARN[0000] Falling back to --cgroup-manager=cgroupfs    
   CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES
   

Describe the results you received

The error message in step 2 is printed twice in step 3.

Describe the results you expected

No duplication of the error message.

podman info output

host:
  arch: arm64
  buildahVersion: 1.37.2
  cgroupControllers:
  - cpu
  - memory
  - pids
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.10-1.fc40.aarch64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.10, commit: '
  cpuUtilization:
    idlePercent: 96.52
    systemPercent: 2.44
    userPercent: 1.04
  cpus: 2
  databaseBackend: sqlite
  distribution:
    distribution: fedora
    variant: coreos
    version: "40"
  eventLogger: journald
  freeLocks: 2046
  hostname: fcos-next5
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 524288
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 524288
      size: 65536
  kernel: 6.10.7-200.fc40.aarch64
  linkmode: dynamic
  logDriver: journald
  memFree: 3392077824
  memTotal: 4082122752
  networkBackend: netavark
  networkBackendInfo:
    backend: netavark
    dns:
      package: aardvark-dns-1.12.1-1.fc40.aarch64
      path: /usr/libexec/podman/aardvark-dns
      version: aardvark-dns 1.12.1
    package: netavark-1.12.2-1.fc40.aarch64
    path: /usr/libexec/podman/netavark
    version: netavark 1.12.2
  ociRuntime:
    name: crun
    package: crun-1.15-1.fc40.aarch64
    path: /usr/bin/crun
    version: |-
      crun version 1.15
      commit: e6eacaf4034e84185fd8780ac9262bbf57082278
      rundir: /run/user/1000/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
  os: linux
  pasta:
    executable: /usr/bin/pasta
    package: passt-0^20240821.g1d6142f-1.fc40.aarch64
    version: |
      pasta 0^20240821.g1d6142f-1.fc40.aarch64-pasta
      Copyright Red Hat
      GNU General Public License, version 2 or later
        <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
      This is free software: you are free to change and redistribute it.
      There is NO WARRANTY, to the extent permitted by law.
  remoteSocket:
    exists: false
    path: /run/user/1000/podman/podman.sock
  rootlessNetworkCmd: pasta
  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: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.2.2-2.fc40.aarch64
    version: |-
      slirp4netns version 1.2.2
      commit: 0ee2d87523e906518d34a6b423271e4826f71faf
      libslirp: 4.7.0
      SLIRP_CONFIG_VERSION_MAX: 4
      libseccomp: 2.5.5
  swapFree: 0
  swapTotal: 0
  uptime: 0h 2m 46.00s
  variant: v8
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
store:
  configFile: /var/home/core/.config/containers/storage.conf
  containerStore:
    number: 2
    paused: 0
    running: 0
    stopped: 2
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /var/home/core/.local/share/containers/storage
  graphRootAllocated: 26238496768
  graphRootUsed: 23703236608
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Supports shifting: "false"
    Supports volatile: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 6
  runRoot: /run/user/1000/containers
  transientStore: false
  volumePath: /var/home/core/.local/share/containers/storage/volumes
version:
  APIVersion: 5.2.2
  Built: 1724198400
  BuiltTime: Wed Aug 21 00:00:00 2024
  GitCommit: ""
  GoVersion: go1.22.6
  Os: linux
  OsArch: linux/arm64
  Version: 5.2.2

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

Yes

Additional environment details

No response

Additional information

No response