podman: podman remote flag/overlay check (regression?)

/kind bug

Description

Running podman --remote in a container doesn’t work anymore in v2.0.5 (worked in v2.0.1) (not tested on versions between v2.0.1 and v2.0.5 yet)

Steps to reproduce the issue:

1. run a podman remote service (podman system service --timeout=0)

2. run a container which bind mounts the socket (/run/podman/podman.sock)

3. run podman <any command> --remote (eg podman images --remote)

Describe the results you received:

podman images --remote
Error: unknown flag: --remote

podman --remote images
Error: 'overlay' is not supported over overlayfs, a mount_program is required: backing file system is unsupported for this graph driver

Describe the results you expected:

this is using v2.0.1 in the container

bash-4.4# podman images --remote
REPOSITORY                                              TAG     IMAGE ID      CREATED       SIZE
registry.centos.org/centos                              8       0cfc5d6fad87  3 months ago  228 MB
registry.centos.org/centos                              7       8114e7c1868b  3 months ago  210 MB
docker.io/library/ubuntu                                latest  1d622ef86b13  4 months ago  76.3 MB

Additional information you deem important (e.g. issue happens only occasionally):

This worked fine in podman v2.0.1 I’ve upgraded to v2.0.5 and it stopped working

Output of podman version:

podman version
Error: 'overlay' is not supported over overlayfs, a mount_program is required: backing file system is unsupported for this graph driver

Output of podman info --debug:

podman info --debug
Error: 'overlay' is not supported over overlayfs, a mount_program is required: backing file system is unsupported for this graph driver

Package info (e.g. output of rpm -q podman or apt list podman):

rpm -q podman
podman-2.0.5-1.el8.x86_64

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?

Yes, latest (released) version of podman, no not checked podman troubleshooting guide.

Additional environment details (AWS, VirtualBox, physical, etc.):

Running podman in a container talking to a remote podman on the same host using bind mount podman socket.