docker-net-dhcp VS docker-pihole-unbound

I tried this Plugin devplayer0/docker-net-dhcp: Docker network driver for networking on a host bridge with DHCP-allocated IP addresses (github.com) but also had Issue #12.

Thanks for this hint. While looking at this I also came across docker-net-dhcp. Though I'll have to check how they behave on a truenas update.

I am using raspsberry pi as a docker host. Though, I was able to create some virtual IP's in my host machine, but that not actually doing what I wanted to. So, is it possible to achieve through some short of plugin? Its possible on podman via CNI plugins leasing ips podman . But, something like that on docker would be very useful for my projects. There is a plugin docker net dhcp, but its x86 only, also there is another experimental driver experimental libinetwork driver that I am not sure how to install or it is also x86. Any help will be highly appreciated.

docker net dhcp : This shows error : pi@raspberrypi:~ $ sudo docker plugin ls ID NAME DESCRIPTION ENABLED c9ff714bd90b devplayer0/net-dhcp:latest Docker host bridge DHCP networking false pi@raspberrypi:~ $ sudo docker plugin enable c9ff714bd90b Error response from daemon: dial unix /run/docker/plugins/c9ff714bd90b282648abed6a833812ad1a6e56d5cdfa1270a80046c4acc98eae/net-dhcp.sock: connect: no such file or directory

I'm running the chriscrowe 'one container' build for pihole for ad-blocking (https://github.com/chriscrowe/docker-pihole-unbound), and unbound for private recursive DNS which is running great on my Zima board.

I believe my problem stems from when I tried to install the pihole-unbound container (https://github.com/chriscrowe/docker-pihole-unbound)

I've got lucky enough that I could get in Nov-19 a Raspberry Pi 4 with 4GB of RAM that I use as a NAS+Pi-Hole + Unbound +Other stuff (running Void MUSL of course) and instead of an SD I use an HDD for the OS + a 5TB HDD for the data and even fully loaded all cores it barely consumes more than 22W.

I was only able to get pihole macvlan approach working with an ssh access + docker-compose approach. I used the crowe one-container approach Still had to enable Open vSwitch for the network in Synology first.

You can follow the doc to do those install steps within your own Dockerfile. Or you can use the commonly recommended chriscrowe image, which does what I’m describing.

When I started experimenting with this topic chriscrowe's was a baseline for stuff that I tryed out, so kudos to chris!

It seems you’re looking at a wrong file. Here is a docker file for one-container solution: https://github.com/chriscrowe/docker-pihole-unbound/blob/55c88afaf8d76958923adc38f4c12a80e1cb9084/one-container/pihole-unbound/Dockerfile

2) you can use something like this maintained GitHub repo. Just decide if you want to use 1 or 2 containers and modify the ip and gateways, etc accordingly.