Does this affect pihole in docker as well? Or only the bare metal install of pihole next to omv, because that was never the correct way if i remember correct.
I guess it will as well becasue it also tries to occupy port 53.
Does this affect pihole in docker as well? Or only the bare metal install of pihole next to omv, because that was never the correct way if i remember correct.
I guess it will as well becasue it also tries to occupy port 53.
Then it is not possible to run any DNS server on the same machine as OMV? Since is suspect they al want to bind to port 53.
If you use a VM, then it shouldn't be a problem. systemd-networkd with systemd-resoved is using internally a proxy which is listening on 53.
Then it is not possible to run any DNS server on the same machine as OMV? Since is suspect they al want to bind to port 53.
See the guide from raulfg3
You can run it on docker with a macvlan.
Or, if you don't need Pihole DHCP server, bind the IP on the YML.
If you use a VM
my hardware isn't really high power so I think a vm is a little overkill for something like pihole
Can a macvlan in docker be a solution?
I am researching at the moment
Edit: apparently Soma posted at almost the same moment as me. I'll have a look at the guide!
Thank you all!!!
Alles anzeigenmy hardware isn't really high power so I think a vm is a little overkill for something like pihole
Can a macvlan in docker be a solution?
I am researching at the moment
Edit: apparently Soma posted at almost the same moment as me. I'll have a look at the guide!
Thank you all!!!
You can also use an lxc to run pihole. lxc essentially same structure that docker works on, but is in between docker and a vm in that it is very minimalistic and light weight like docker, but is it's own virtual machine and gives easier shell access for customization like a full vm would.
You can also use an lxc to run pihole.
Good to hear! Would you have details on memory consumption (which seems the most limiting factor on SBCs)?
Good to hear! Would you have details on memory consumption (which seems the most limiting factor on SBCs)?
my lxc pihole uses about 167MB of RAM, even though I have it configured for 2 CPU's and 1GB maximum.
re "use an lxc to run pihole" is there perhaps a pointer to a doc for getting it setup this way?
re "use an lxc to run pihole" is there perhaps a pointer to a doc for getting it setup this way?
The omv-KVM plugin provides LXC container templates. So I guess you just need to install pi-hole on Debian or Ubuntu.
The omv-KVM plugin provides LXC container templates. So I guess you just need to install pi-hole on Debian or Ubuntu.
This is correct. In the KVM plugin make an lcx with a debian or ubuntu base and install pihole on that. You should make a macvtap noc in hvm so that the lxc can be assigned to it and get a different IP address form your server to avoid port 53 conflicts.
Just a note regarding the lcx's. The base that they start from is extremely stripped down (hence the low ram usage), so you may find that would want to install a few extra things too, such as openssh-server so you can ssh into them, and perhaps a few other admin style tools if you have any you like.
my lxc pihole uses about 167MB of RAM, even though I have it configured for 2 CPU's and 1GB maximum.
Pihole together with Unbound consume about 500MB of RAM here. I also installed Folder2Ram. The logs are written to RAM.
Pihole together with Unbound consume about 500MB of RAM here. I also installed Folder2Ram. The logs are written to RAM.
I am not using unbound, just the simple dnsmasq that is in Pihole. I would assume unbound is more resource intensive since it is a true dns service while dnsmasq is a dns redirect
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!