Repository navigation
Fix: say what makes a socket proxy address reachable - #43
Merged
Merged
Conversation
A socket proxy address fails for one of two opposite reasons, and neither error text distinguishes them. A service name is resolved by Docker's DNS, which answers only for containers sharing a network; an IP reaches only what the proxy published, and the usual compose publishes on the host's loopback, which no container can reach at any address. The probe now returns which shape the address is, and the save reports the matching remedy alongside the error. The settings hint states both rules before the mistake is made and links to the troubleshooting section, which gains the compose fragments for each fix. A timeout on a literal address is now refused rather than warned about. Packets to a port bound on another namespace's loopback are dropped rather than refused, so the commonest wrong address arrived as a timeout and saved quietly under the old rule.
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
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.
Summary
hintfromPOST /api/docker/testnaming which address shape failed: a service name needing a shared Docker network, or an address needing its port published where a container can reach it.network_mode: bridgeresolves no service name and why0.0.0.0is worth avoiding.Testing
All green. Added 3 tests covering both hints and the timeout reclassification.
Checklist