Update running-gatewayd.md to handle Docker host connection for different setups #56
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses the issue of setting the Docker host variable when running on Docker Desktop. Due to the networking implementation in Docker Desktop, the
docker0
bridge interface is not present on the host. Instead, we can use the DNS name (https://docs.docker.com/desktop/networking/#use-cases-and-workarounds)Changes Made
DOCKER_HOST
variable tohost.docker.internal
when using Docker Desktop.Context
When running on Docker Desktop, the absence of the docker0 bridge interface on the host can lead to confusion regarding how to correctly set up the Docker host variable.