Investigate purpose of Docker socket API

[mfarina1]

For Podman, is the Docker socket API truly only used for the mapping of Docker's socket, so that one of the containers can query the status of Docker services? Currently it's not working, but the real question is if it's doing anything other than monitoring the various Docker services? If that's all it's doing, there's probably a better way of doing it that's less dependent on infrastructure

[mfarina1]

Comment from David Edell: "The only piece I’ve seen so far that is specific to docker is the mounted docker.sock that I suspect is only being used to drive the “Services” status page in the ANMS UI. I believe there is a way podman on the host system can be configured to preserve that functionality. If that is the only thing that socket is used for though, it would probably make more sense in the long-term to replace it with something more generic (which could also work if the components are later distributed to physical systems). "

[DavidEdell]

There is no indication that the socket API is used for anything other than reporting container status in anms-core.

See #143 for additional details.