.The linger feature can be canceled for the correct users When processing the instruction list of configuration items from kube files or Quadlet files, the `podman` RHEL system role was incorrectly using the user ID associated with the entire list. It did not use the user ID associated with the list item to compile the linger file name. Consequently, the linger file was not created and therefore the `podman` RHEL system role could not cancel the linger feature for the actual user if necessary. With this update, `podman` uses the correct username to construct the linger file name. As a result, the linger feature can be canceled for the correct users.