20220118 networking - master branch - PR 1 of 2

This PR follows on from [Issue 422](#422 (comment)) and the networking scheme proposed therein to support remote WireGuard clients obtaining DNS from ad-blockers (eg PiHole) running in another container on the same RPi as the WireGuard server.

This PR implements:

1. Two internal networks:

	* "default" (`iotstack_default` at runtime).
	* "nextcloud" (`iotstack_nextcloud` at runtime).

2. Docker allocates all IP addressing, dynamically, from 172.16/12 (reverting from 10/8 subnets).
3. NextCloud *explicitly* joins both internal networks.
4. NextCloud_DB *explicitly* joins "nextcloud".
5. All other containers *implicitly* join "default".
6. No networking differences between old and new menus (full harmonisation).
7. Resolves all remaining new-menu inconsistencies first raised in [Issue 245](#245).

Adds `use-container-dns.sh` to WireGuard service template folder to support WireGuard forwarding DNS requests to ad-blockers running on the same RPi. This is based on work done by @ukkopahis. This change is related to the networking changes which deviate from the scheme proposed in Issue 422.

Documentation:

1. Adds "significant change to networking" to main README.md.
2. Updates WireGuard to explain how to forward DNS requests to ad-blockers running on the same RPi.

Signed-off-by: Phill Kelley <[email protected]>

Author: Paraphraser

.templates/adguardhome/service.yml

@@ -30,6 +30,4 @@ adguardhome:
   volumes:
      - ./volumes/adguardhome/workdir:/opt/adguardhome/work
      - ./volumes/adguardhome/confdir:/opt/adguardhome/conf
-  networks:
-    - iotstack_nw
-    - vpn_nw
+

.templates/adminer/service.yml

@@ -4,5 +4,4 @@ adminer:
   restart: unless-stopped
   ports:
     - "9080:8080"
-  networks:
-    - iotstack_nw
+

.templates/blynk_server/service.yml

@@ -16,5 +16,4 @@ blynk_server:
   volumes:
     - ./volumes/blynk_server/data:/data
     - ./volumes/blynk_server/config:/config
-  networks:
-    - iotstack_nw
+

.templates/chronograf/service.yml

@@ -17,5 +17,4 @@ chronograf:
   depends_on:
     - influxdb
   # - kapacitor
-  networks:
-    - iotstack_nw
+

.templates/dashmachine/service.yml

@@ -6,3 +6,4 @@ dashmachine:
   ports:
     - 5000:5000
   restart: unless-stopped
+

.templates/deconz/service.yml

@@ -18,6 +18,5 @@ deconz:
     - DEBUG_ZCL=0
     - DEBUG_ZDP=0
     - DEBUG_OTAU=0
-  networks:
-    - iotstack_nw
+
 

.templates/diyhue/service.yml

@@ -12,5 +12,4 @@ diyhue:
   volumes:
       - ./volumes/diyhue:/opt/hue-emulator/export
   restart: unless-stopped
-  networks:
-    - iotstack_nw
+

.templates/domoticz/service.yml

@@ -14,3 +14,4 @@ domoticz:
     - PGID=1000
     # - TZ=
     # - WEBROOT=domoticz
+

.templates/dozzle/service.yml

@@ -7,3 +7,4 @@ dozzle:
   # - "8888:8080"
   volumes:
     - /var/run/docker.sock:/var/run/docker.sock
+

.templates/env.yml

@@ -1,42 +1,13 @@
 networks:
-  iotstack_nw: # Exposed by your host.
-    # external: true
-    name: IOTstack_Net
+
+  default:
     driver: bridge
     ipam:
       driver: default
-      config:
-        - subnet: 10.77.60.0/24
-        # - gateway: 10.77.60.1
 
-  iotstack_nw_internal: # For interservice communication. No access to outside
-    name: IOTstack_Net_Internal
+  nextcloud:
     driver: bridge
     internal: true
     ipam:
       driver: default
-      config:
-        - subnet: 10.77.76.0/24
-        # - gateway: 10.77.76.1
-      
-  vpn_nw: # Network specifically for VPN
-    name: IOTstack_VPN
-    driver: bridge
-    ipam:
-      driver: default
-      config:
-        - subnet: 10.77.88.0/24
-        # - gateway: 192.18.200.1
-
-  nextcloud_internal: # Network for NextCloud service
-    name: IOTstack_NextCloud
-    driver: bridge
-    internal: true
-      
-  # default:
-  #   external: true
-  #   name: iotstack_nw
 
-  # hosts_nw:
-  #   driver: hosts
-