Comment 1 for bug 1923607

Interestingly if we inspect a normal "podman" process we see:
PID: 846098 TASK: ffff9c20fd8ddc40 CPU: 1 COMMAND: "podman"
ARG: /usr/bin/podman --root /var/lib/containers/storage --runroot /var/run/containers/storage --log-level error --cgroup-manager systemd --tmpdir /var/run/libpod --runtime runc --storage-driver overlay --storage-opt overlay.mountopt=nodev,metacopy=on --events-backend file container cleanup 881e8ef19bb5e57de90c1fb2a784f821934707b1075c44452e2e355b9df3aba7
ENV: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
     _OCI_SYNCPIPE=3
     _OCI_STARTPIPE=4
     XDG_RUNTIME_DIR=
     _CONTAINERS_USERNS_CONFIGURED=
     _CONTAINERS_ROOTLESS_UID=

But those '(podman)' processes do not show any arguments nor env variables:
PID: 846103 TASK: ffff9c20f8aa1ec0 CPU: 1 COMMAND: "(podman)"
ARG: (podman)
ENV: HOME=/
     TERM=vt220
     BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-4.18.0-240.10.1.el8_3.x86_64
     crashkernel=auto