Bug 2028439

Description of problem:
podman run with --rm will report "device or resource busy" with NFS storage. The same error will also be report when try to remove a running container with -f. They should be similar problem.

Version-Release number of selected component (if applicable):
podman-3.4.3-0.7.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. mount NFS to /var/lib/containers/storage to let podman use NFS storage
2. RUN a container with --rm or start a container then try to remove it with -f
# podman run --rm quay.io/libpod/busybox sleep 2

or 

# podman run -d quay.io/libpod/busybox sleep 99
# podman rm -f $cid


Actual results:
Error message is raise by the command line, and the command finished with status 125.

ERRO[0002] Error removing container 5d4d1f0166c5d08db7b1f95b7185214aa0c4324b2848cc346e57badea593d9de: error removing container 5d4d1f0166c5d08db7b1f95b7185214aa0c4324b2848cc346e57badea593d9de root filesystem: 2 errors occurred:
	* unlinkat /var/lib/containers/storage/overlay-containers/5d4d1f0166c5d08db7b1f95b7185214aa0c4324b2848cc346e57badea593d9de/userdata/.nfs0000000006138ca5000003b1: device or resource busy
	* unlinkat /var/lib/containers/storage/overlay-containers/5d4d1f0166c5d08db7b1f95b7185214aa0c4324b2848cc346e57badea593d9de/userdata/.nfs0000000006138ca5000003b1: device or resource busy

Expected results:
container can be delete without the error message

Additional info:

We can remove a stopped container successfully. And if we checked the container status with podman ps -a after the command finished. We can see that the container is actually removed.