podman cp system tests flake under VFS, with pretty consistent symptoms:

not ok podman cp XXXXX
...
# podman cp something
Error: "/tmp/sub/weirdlink" could not be found on container cpcontainer: no such file or directory

or

# podman cp cpcontainer:/srv b55ec9a6aadd4d115ff483614fd5ac7e606acfb09b6a4516883538eca3357893:/
(works)
# podman exec b55ec9a6aadd4d115ff483614fd5ac7e606acfb09b6a4516883538eca3357893 cat //srv/subdir/containerfile0 //srv/subdir/containerfile1
random-0-QrZE7sZYZs     <------ this is containerfile0
cat: can't open '//srv/subdir/containerfile1': No such file or directory

I've been chasing this one all week because it's a hard blocker for #20161. It's a BAD flake, failing on almost every run, and pretty easily reproducible in 1minutetip. Despite my hopes this morning in seeing containers/storage#1724, that does not fix the problem: the 10-05 failures below include a vendored c/storage.

• fedora-38 : sys podman fedora-38 root host boltdb
  • PR CI: test overlay and vfs #20161
    • 10-05 16:31 in [sys] podman cp symlinked directory from container
    • 10-02 15:22 in [sys] podman cp dir from container to container
• fedora-38 : sys podman fedora-38 root host sqlite
  • PR Ed's pet PR with no flake retries #17831
    • 10-05 16:25 in [sys] podman cp file from container to container
    • 10-05 16:25 in [sys] podman cp dir from container to container
• fedora-38 : sys podman fedora-38 rootless host sqlite
  • PR Ed's pet PR with no flake retries #17831
    • 10-05 16:22 in [sys] podman cp file from container to container
    • 10-05 16:22 in [sys] podman cp dir from container to container
• fedora-38 : sys remote fedora-38 root host boltdb [remote]
  • PR CI: test overlay and vfs #20161
    • 10-04 14:15 in [sys] podman cp file from container to container
    • 10-03 12:23 in [sys] podman cp file from container to container
• fedora-38 : sys remote fedora-38 root host sqlite [remote]
  • PR Ed's pet PR with no flake retries #17831
    • 10-05 16:12 in [sys] podman cp file from container to container
    • 10-05 16:12 in [sys] podman cp dir from container to container
    • 10-05 16:12 in [sys] podman cp symlinked directory from container
    • 10-05 16:12 in [sys] podman cp into container: weird symlink expansion
    • 10-05 16:12 in [sys] podman cp - dot notation - container to host

Seen in: podman/remote fedora-38 root/rootless boltdb/sqlite

"fedora-38" is only special because that's prior-fedora which means force VFS under the rules of #20161. It could possibly be a kernel or distro bug only on f38, but I choose not to even bother considering that right now. I'm treating it as a VFS driver bug.