472
The Beauty Of Having A Pi-hole · Den Delimarsky (den.dev)
submitted 1 year ago by to c/technology@lemmy.world
117 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 38 points 1 year ago* (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 21 points 1 year ago* (last edited 1 year 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/

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 1 year ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •