Route container host-gateway to loopback on Windows#6859
Open
Badbird5907 wants to merge 1 commit into
Open
Conversation
The container egress listener binds to the address returned by gatewayForPlatform. On macOS it returns none (falls back to loopback) because Docker Desktop routes the host-gateway through a VM; every other platform got the Docker bridge gateway IP. On Windows the bridge IP is not a local interface on the host, so the bind fails and container start() aborts. Windows Docker Desktop behaves like macOS, so include _WIN32 in the loopback branch.
|
All contributors have signed the CLA ✍️ ✅ |
5 tasks
Author
|
I have read the CLA Document and I hereby sign the CLA |
petebacondarwin
approved these changes
Jul 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The container egress listener binds to the address returned by gatewayForPlatform. On macOS it returns none (falls back to loopback) because Docker Desktop routes the host-gateway through a VM; every other platform got the Docker bridge gateway IP. On Windows the bridge IP is not a local interface on the host, so the bind fails and container start() aborts. Windows Docker Desktop behaves like macOS, so include _WIN32 in the loopback branch.
This is to add support for local container dev on windows machines. (cloudflare/workers-sdk#14566)