Makes wireguard point to pihole by default #109
Conversation
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
|
@cappe This isn't necessary anymore since the project was switched away from using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 spent a while for trying to understand why the PiHole was not working by default. The project description let me understand that it's virtually
docker compose upand you are good to go.I noticed that the
WG_DEFAULT_DNSpoints to CloudFlare (1.1.1.1) by default. When changing it to- WG_DEFAULT_DNS=10.2.0.100anddocker compose up, everything worked as expected.To make the project easier to setup — especially for beginners — I'm proposing adding this default value to the
docker-compose.yml.