this post was submitted on 05 May 2025
463 points (98.3% liked)

Technology

69845 readers
3710 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
463
The Beauty Of Having A Pi-hole · Den Delimarsky (den.dev)
submitted 2 days ago by fusspilz@feddit.org to c/technology@lemmy.world
118 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] normalexit@lemmy.world 37 points 2 days ago* (last edited 2 days ago) (1 children)

If you have a server running, I wouldn't buy more hardware. They have good example documentation for just such a configuration:

https://docs.pi-hole.net/docker/

If your server already has those ports bound (specifically the DNS port 53) you are going to have to get creative; otherwise it'll work well!

Worst case, a cheapo pi 3 will do the job. At one point I had it running on a pi zero, so hardware requirements are pretty low.

[–] PoopMonster@lemmy.world 21 points 2 days ago* (last edited 1 day ago) (2 children)

If your using docker and the ports are bound you can just use the network mode host so the container gets it's own ip. It's how I have adguard running on my unraid server

edit: Sorry I mixed up the details as @starkzarn@infosec.pub pointed out. It's a macvlan configuration. My intention was to point out it's possible. Here's some documentation https://docs.docker.com/engine/network/drivers/macvlan/

[–] starkzarn@infosec.pub 2 points 1 day ago (1 children)

That's not how that works. network_mode: host shares the network namespace with the container host, so it doesn't do any NAT, it only exists on the host's IP. It would be akin to running a natively installed app, rather than in a container. macvlan networking is what gives a container its own IP on the logical network, without the layer of NAT that the default bridge mode networking that docker typically does.

[–] PoopMonster@lemmy.world 2 points 1 day ago

Thanks for the clarification I had mixed up the details and went to check my containers. You sir are correct. I added some documentation to my post regarding macvlan network creation.

[–] normalexit@lemmy.world 10 points 2 days ago* (last edited 2 days ago)

Thanks, PoopMonster, that's a good tip!