Describe the bug
A clear and concise description of what the bug is.

OS: MacOS
CPU Arch: M1
podman-compose version: 1.5.0

When running a docker-compose that includes the following

volumes:
  - /var/run/docker.sock:/var/run/docker.sock

running podman compose up results in the following error:

Error: statfs /private/var/folders/0f/y6yk5ngd4r1_3wy0_5qf46xr0000gp/T/podman/podman-machine-default-api.sock: operation not supported

I believe this to be the result of calling os.path.realpath on the mount_src inside assert_volume rather than calling os.path.abspath. Switching the os.path.realpath call out in favor of os.path.abspath appears to fix the issue for me locally.

Please make sure it's not a bug in podman (in that case report it to podman)
or your understanding of docker-compose or how rootless containers work (for example, it's normal for rootless container not to be able to listen for port less than 1024 like 80)

To Reproduce
Steps to reproduce the behavior:

1. on MacOS M1
2. any docker-compose that includes a container with the following volume mount:

   volumes:
     - /var/run/docker.sock:/var/run/docker.sock
   

3. podman compose up

Expected behavior
Container is created and volume is mounted to the container

Actual behavior

Error: statfs /private/var/folders/0f/y6yk5ngd4r1_3wy0_5qf46xr0000gp/T/podman/podman-machine-default-api.sock: operation not supported

Output

$ podman-compose version
podman-compose version 1.5.0
podman version 5.6.0
podman --version 
podman version 5.6.0

$ podman-compose up
...

Environment:

• OS: Mac
• podman version: 5.6.0
• podman compose version: 1.5.0

Additional context

Add any other context about the problem here.