feat: forward guest DNS to Docker's embedded resolver#793
Open
alimx07 wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for urunc ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
alimx07
force-pushed
the
feat/add-docker-dns
branch
2 times, most recently
from
June 28, 2026 07:44
25a6350 to
a743f29
Compare
alimx07
force-pushed
the
feat/add-docker-dns
branch
from
July 10, 2026 15:49
a743f29 to
6723c67
Compare
Author
|
Hey @cmainas, I have implemented the changes we discussed during our sync. Could you please take a look and review them? This will allow us to make any necessary changes before we extend this logic to other unikernels. |
alimx07
force-pushed
the
feat/add-docker-dns
branch
2 times, most recently
from
July 19, 2026 04:53
c1faf48 to
861d5e4
Compare
On Docker user custom networks the DNS resolver (127.0.0.11) is loopback only and unreachable by the unikernel guest. Detect this case per container, expose the resolver via a virtual resolver IP using tc redirects between the tap and lo + a PREROUTING DNAT, and rewrite the guest's resolv.conf to point at that IP. Signed-off-by: Ali Mohamed <amx746@gmail.com>
alimx07
force-pushed
the
feat/add-docker-dns
branch
from
July 19, 2026 04:57
861d5e4 to
27c8c27
Compare
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.
Description
On Docker user custom networks the DNS resolver (127.0.0.11) is loopback only and unreachable by the unikernel guest. Detect this case per container, expose the resolver via a virtual resolver IP
configured by userusing tc redirects between the tap and lo , and rewrite the guest'sresolv.confto point at that IP in our unikernel islinuxone. Also we add a custom rules DNAT rules according to the enviroment (e.g. Docker -> PREROUTING DNAT(for DNS server ports))Two TC rules added on tap and lo:
src=ResolvIPinto TapRelated issues
How was this tested?
Tested in user custom docker network with urunc container
u1and normal oneu2:u1lookup ongithub.comu1lookup onu2u2lookup onu1LLM usage
Checklist
make lint).make test_ctr,make test_nerdctl,make test_docker,make test_crictl).