You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
alyssadai
added
type:bug
Defects in shipped code and fixes for those defects
someday
Not a priority right now, but we want to keep this around to think or discuss more.
labels
Feb 22, 2024
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.
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 thelocal_node
recipe, which expose a port to the host and should be accessible viahost.docker.internal:<port on host>
.So far, only using the external URL for the n-API (NGINX) in
local_nb_nodes.json
works.Notes:
curl -vv
in a bash terminal inside the container shows thathost.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 reachedThe text was updated successfully, but these errors were encountered: