{"id":1098,"date":"2024-03-18T15:32:42","date_gmt":"2024-03-18T15:32:42","guid":{"rendered":"https:\/\/thomas.w-p.me.uk\/blog\/?p=1098"},"modified":"2024-03-18T15:44:54","modified_gmt":"2024-03-18T15:44:54","slug":"macvlan-with-docker-and-pihole","status":"publish","type":"post","link":"https:\/\/thomas.w-p.me.uk\/blog\/2024\/03\/macvlan-with-docker-and-pihole\/","title":{"rendered":"macvlan with docker and pihole"},"content":{"rendered":"\n

This web page (Set up a PiHole using Docker MacVlan Networks<\/a>) is great and got me there, but here are notes on how I fixed it globally. I use many stacks.<\/p>\n\n\n\n

\n\n\n\n

You need MACVLAN network to fake an external IP for the DNS\/DHCP server or it does not work (the requests don’t come through docker). But if you make a macvlan IP address, by design the host cannot see that IP address! You have to make a bridge.<\/p>\n\n\n\n

If that bridge is local to the docker compose file, then only that stack can see it. For all stacks to see it you need to make a new macvlan and bridge network globally (I did this in portainer).<\/p>\n\n\n\n

Steps to create:<\/p>\n\n\n\n

1. Make a macvlan configuration<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
name<\/span>:<\/span> pihole<\/span>-<\/span>macvlan<\/span>-<\/span>config<\/span><\/span>\nInterface<\/span>:<\/span> eth0<\/span><\/span>\nIPV4 Subnet <\/span>-<\/span> <\/span>192.168<\/span>.<\/span>0.0<\/span>\/<\/span>24<\/span>\tIPV4 Gateway <\/span>-<\/span> <\/span>192.168<\/span>.<\/span>0.1<\/span><\/span>\nIPV4 IP Range <\/span>-<\/span> <\/span>192.168<\/span>.<\/span>0.8<\/span>\/<\/span>29<\/span>\t<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
2. Make the macvlan using that configuration (just select the configuration and give it a name)<\/p>\n\n\n\n
<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
name<\/span>:<\/span> pihole<\/span>-<\/span>macvlan<\/span><\/span>\ndriver<\/span>:<\/span> macvlan<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
3. Set up the bridge<\/p>\n\n\n\n
name: pihole-bridge\nIPV4 Subnet - 10.123.0.0\/24<\/code><\/pre>\n\n\n\n
4. In pihole set up the brige ip address.<\/p>\n\n\n\n
<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
    <\/span>networks<\/span>:<\/span><\/span>\n      pihole<\/span>-<\/span>macvlan<\/span>:<\/span><\/span>\n        <\/span>ipv4_address<\/span>:<\/span> <\/span>192.168<\/span>.<\/span>0.10<\/span><\/span>\n      pihole<\/span>-<\/span>bridge<\/span>:<\/span><\/span>\n        <\/span>ipv4_address<\/span>:<\/span> <\/span>10.123<\/span>.<\/span>0.2<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
5. Use nmtui to change the host “dockerbox” DNS to 10.123.0.2 and give it a fixed IP address. All the containers will look for that for the DNS but need pihole-bridge network to see it.<\/p>\n\n\n\n
<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
sudo nmtui<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
6. In each container that needs pihole you add the network pihole-bridge<\/p>\n\n\n\n
e.g.<\/p>\n\n\n\n
<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
  <\/span>tasmoadmin<\/span>:<\/span><\/span>\n    <\/span>container_name<\/span>:<\/span> tasmoadmin<\/span><\/span>\n    <\/span>image<\/span>:<\/span> ghcr<\/span>.<\/span>io<\/span>\/<\/span>tasmoadmin<\/span>\/<\/span>tasmoadmin<\/span>:<\/span>latest<\/span><\/span>\n    <\/span>volumes<\/span>:<\/span><\/span>\n      <\/span>-<\/span> <\/span>.\/<\/span>tasmoadmin<\/span>-<\/span>data<\/span>:\/<\/span>data <\/span><\/span>\n    <\/span>ports<\/span>:<\/span><\/span>\n      <\/span>-<\/span> <\/span>9541<\/span>:<\/span>80<\/span><\/span>\n    <\/span>restart<\/span>:<\/span> unless<\/span>-<\/span>stopped<\/span><\/span>\n    <\/span>depends_on<\/span>:<\/span><\/span>\n      <\/span>-<\/span> homeassistant<\/span><\/span>\n    <\/span>networks<\/span>:<\/span><\/span>\n      <\/span>-<\/span> mqtt<\/span><\/span>\n      <\/span>-<\/span> pihole<\/span>-<\/span>bridge<\/span><\/span><\/code><\/pre><\/div>\n","protected":false},"excerpt":{"rendered":"
This web page (Set up a PiHole using Docker MacVlan Networks) is great and got me there, but here are notes on how I fixed it globally. I use many stacks. You need MACVLAN network to fake an external IP for the DNS\/DHCP server or it does not work (the requests don’t come through docker). … Continue reading macvlan with docker and pihole<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[110,108],"tags":[],"class_list":["post-1098","post","type-post","status-publish","format-standard","hentry","category-docker","category-home-assistant"],"_links":{"self":[{"href":"https:\/\/thomas.w-p.me.uk\/blog\/wp-json\/wp\/v2\/posts\/1098","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thomas.w-p.me.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thomas.w-p.me.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thomas.w-p.me.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/thomas.w-p.me.uk\/blog\/wp-json\/wp\/v2\/comments?post=1098"}],"version-history":[{"count":2,"href":"https:\/\/thomas.w-p.me.uk\/blog\/wp-json\/wp\/v2\/posts\/1098\/revisions"}],"predecessor-version":[{"id":1102,"href":"https:\/\/thomas.w-p.me.uk\/blog\/wp-json\/wp\/v2\/posts\/1098\/revisions\/1102"}],"wp:attachment":[{"href":"https:\/\/thomas.w-p.me.uk\/blog\/wp-json\/wp\/v2\/media?parent=1098"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thomas.w-p.me.uk\/blog\/wp-json\/wp\/v2\/categories?post=1098"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thomas.w-p.me.uk\/blog\/wp-json\/wp\/v2\/tags?post=1098"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}