Create loopback aliases for inter-container communication#62
Open
jonscheiding wants to merge 2 commits intoFreedomBen:masterfrom
Open
Create loopback aliases for inter-container communication#62jonscheiding wants to merge 2 commits intoFreedomBen:masterfrom
jonscheiding wants to merge 2 commits intoFreedomBen:masterfrom
Conversation
Author
|
@FreedomBen 👋 any interest in this change? |
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
1 participant
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.
I've used Dory on a Mac for awhile, and to level up its usefulness, I've configured it to respond to DNS queries with a private IP address, and configured said address as an alias for the loopback interface. This allows containers to communicate with each other - even if they're on a bridge network - using the same names that I use to talk to them from the host, which can simplify a lot of situations.
I thought it might be nice to have Dory handle this itself, it seems within the scope of what a development proxy would do.
If interested in this PR I can look into how to support it on Linux.
(Also included is a configuration option to keep the containers running across Docker/computer restarts)