From e5feba48c8f87f9a27db19c13e73cd3813567687 Mon Sep 17 00:00:00 2001 From: Adam Hill Date: Sat, 9 Feb 2019 13:42:05 -0600 Subject: [PATCH] Forgot a citation and alternative to doco for default bridge Signed-off-by: Adam Hill --- docs/docker/DHCP.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/docker/DHCP.md b/docs/docker/DHCP.md index e64fcca..c6f2ddb 100644 --- a/docs/docker/DHCP.md +++ b/docs/docker/DHCP.md @@ -31,14 +31,14 @@ Having the container get it's own IP not only solves the broadcast problem but a ### Docker Pi-hole with a bridge networking -If you want to use docker's bridged network mode then you need to run a DHCP relay. A relay points to your containers forwarded port 67 and spreads the broadcast signal from isolated docker bridge onto your LAN network. Relays are very simple software, you just have to configure it to point at your Docker host's IP port 67. +If you want to use docker's bridged network mode then you need to run a DHCP relay. A relay points to your containers forwarded port 67 and spreads the broadcast signal from isolated docker bridge onto your LAN network. Relays are very simple software, you just have to configure it to point at your Docker host's IP port 67. Although uncommon, if your router is advanced enough router it may support a DHCP relay. Try googling for your router manufacturer + DHCP relay or looking in your router's configuration around the DHCP settings or advanced areas. -If your router doesn't support it, you can run a software / container based DHCP relay on your LAN instead. The author of DNSMasq made a very tiny simple one called [dhcp-helper](http://thekelleys.org.uk/dhcp-helper/READ-ME). [DerFetzer](https://discourse.pi-hole.net/t/dhcp-with-docker-compose-and-bridge-networking/17038) kindly shared his great setup of a DHCP-helper container on the Pi-hole discourse forums. +If your router doesn't support it, you can run a software / container based DHCP relay on your LAN instead. The author of DNSMasq made a very tiny simple one called [dhcp-helper](http://thekelleys.org.uk/dhcp-helper/READ-ME). [DerFetzer](https://discourse.pi-hole.net/t/dhcp-with-docker-compose-and-bridge-networking/17038) kindly shared his great setup of a DHCP-helper container on the Pi-hole discourse forums. ### Warning about the Default bridge network -The out of the box default bridge newtork has some limitations that a user created bridge network won't have. These limitations make it painful to use especially when connecting multiple containers together. +The out of the box [default bridge newtork has some limitations](https://docs.docker.com/network/bridge/#differences-between-user-defined-bridges-and-the-default-bridge) that a user created bridge network won't have. These limitations make it painful to use especially when connecting multiple containers together. -Avoid using the built in default docker bridge newtork, the simplest way to do this is just use a docker-compose setup since it creates it's own network automatically. +Avoid using the built in default docker bridge newtork, the simplest way to do this is just use a docker-compose setup since it creates it's own network automatically. If compose isn't an option the [bridge network](https://docs.docker.com/network/bridge/) docs should help you create your own.