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
Currently suggest using 192.18.0.1 to access host from within container.
This really only works when user does not have any other networks defined and is spinning up a Dashtainer project on a vanilla host. If any other networks defined that IP is no longer valid.
Using route | awk '/^default/ { print $2 }' we can find the gateway that can be used for Xdebug (and other services that must reach host!).
Windows and MacOS can use docker.for.mac.host.internal, docker.for.win.host.internal. Maybe create an entry in /etc/hosts for containers that need this?
Currently suggest using 192.18.0.1 to access host from within container.
This really only works when user does not have any other networks defined and is spinning up a Dashtainer project on a vanilla host. If any other networks defined that IP is no longer valid.
Using
route | awk '/^default/ { print $2 }'
we can find the gateway that can be used for Xdebug (and other services that must reach host!).Windows and MacOS can use
docker.for.mac.host.internal
,docker.for.win.host.internal
. Maybe create an entry in/etc/hosts
for containers that need this?The text was updated successfully, but these errors were encountered: