Switch to go-dnsmasq as local DNS resolver#7
Open
janeczku wants to merge 1 commit into
Open
Conversation
Member
|
Hey sorry I've been off line for a little while I'm taking a look at your suggestion which seems like a very good one. |
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.
I propose a streamlined approach to fix the DNS limitation of musl-libc based Docker containers by replacing dnsmasq and all the DNS workaround scripts with https://github.com/janeczku/go-dnsmasq.
This is essentially a slimmed down Golang fork of dnsmasq that has a feature to replicate the
resolv.confsearch keywordfunctionality.Advantages:
You may try it out with the
docker-composer.ymlortutum.ymlin the branch of this PR: https://github.com/janeczku/base-alpine/tree/go-dnsmasq