Containers on neurobagel-node cannot access services on host via host.docker.internal

[alyssadai]

When an f-API is deployed on this machine in either a standalone container on the default bridge network, or via our local_federation recipe, it cannot access services like the n-API from the local_node recipe, which expose a port to the host and should be accessible via host.docker.internal:<port on host>.

So far, only using the external URL for the n-API (NGINX) in local_nb_nodes.json works.

Notes:

• Running curl -vv in a bash terminal inside the container shows that host.docker.internal successfully resolves to whatever the default bridge network IP address is, but services with published ports on the host still can't be reached

[alyssadai]

We don't plan to investigate this further for now since we've moved away from using a VM with a NFS due to various issues and quirks associated with that setup. This is also a server scenario that's unlikely to be common among deploying institutes.