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

Fixes dnsmasq on Fedora systems #185

Closed
wants to merge 1 commit into from
Closed

Fixes dnsmasq on Fedora systems #185

wants to merge 1 commit into from

Conversation

superterran
Copy link

points networkmanager to dhclient service to enable dnsmasq support on fedora

@davidalger davidalger added the enhancement New feature or request label Jul 22, 2020
@davidalger
Copy link
Collaborator

Thanks for the PR @superterran! I'm strongly considering stripping out the attempted auto-configuration of DNS resolver on Linux both to not muck with users configuration (which can be very a personal thing on Linux systems) as well as to resolve the warnings the systemd checks end up issuing when you try and run Warden either within a docker container (for DIND setups) and on WSL2.

The replacement would be something along the lines of this documentation from another project: https://devilbox.readthedocs.io/en/latest/intermediate/setup-auto-dns.html

@superterran
Copy link
Author

I think that's a good call, I've tested this config for about a week in Fedora and while it works for warden, it removes the ability to discover linux hostnames on the local network. This seems to be true for Ubuntu as well.

davidalger added a commit that referenced this pull request Feb 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants