Drop external_services network and create a network for each public service #185

New issue

Closed

opened 2023-12-12 20:41:42 +00:00 by samsapti · 1 comment

samsapti commented

2023-12-12 20:41:42 +00:00

Owner

Instead of having one big external_services Docker network, we should create one network for each container that should be publicly reachable through nginx-proxy, and then add nginx-proxy to each of those networks. This avoids issues like the one fixed in commit dfcca8a3e9 where two containers from two different Compose stacks had the same DNS name, and Mailu decided to resolve admin to the OpenLDAP admincontainer instead of Mailu admin container.

Instead of having one big `external_services` Docker network, we should create one network for each container that should be publicly reachable through nginx-proxy, and then add nginx-proxy to each of those networks. This avoids issues like the one fixed in commit dfcca8a3e9bc0c58a2367147ea6be37f10d7ff77 where two containers from two different Compose stacks had the same DNS name, and Mailu decided to resolve `admin` to the OpenLDAP `admin`container instead of Mailu `admin` container.