Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use internal resolver for default bridge #48027

Open
robmry opened this issue Jun 18, 2024 · 0 comments
Open

Use internal resolver for default bridge #48027

robmry opened this issue Jun 18, 2024 · 0 comments
Labels
area/networking/d/bridge area/networking/dns area/networking kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny
Milestone

Comments

@robmry
Copy link
Contributor

robmry commented Jun 18, 2024

Description

Related to:

#47602 set up the internal resolver for the default bridge, removing the need for checking whether systemd's resolver is running (to find its upstream requests), making it possible to use an IPv6 upstream server from an IPv4 network, removing the need for fallback servers when the host's DNS servers aren't reachavle from the container - and generally making the default bridge more like a custom bridge.

That change was reverted in #48020 because buildkit doesn't run an internal resolver (or DNS forwarder), so containerised buildkit could end up using the Google fallback servers, when it would previously have used a local DNS server.

We need to come up with a plan for restoring the change, and do that.

@robmry robmry added kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny area/networking area/networking/d/bridge area/networking/dns labels Jun 18, 2024
@robmry robmry added this to the 28.0.0 milestone Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking/d/bridge area/networking/dns area/networking kind/feature Functionality or other elements that the project doesn't currently have. Features are new and shiny
Projects
None yet
Development

No branches or pull requests

1 participant