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

Closed
opened 2023-12-12 20:41:42 +00:00 by samsapti · 1 comment
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.
samsapti added the
Infrastructure Issue
label 2023-12-12 20:41:42 +00:00
samsapti self-assigned this 2023-12-12 21:10:00 +00:00
Author
Owner

This means that we would need to restart NGINX every time we add a new service.

This means that we would need to restart NGINX every time we add a new service.
valberg added this to the Devops work project 2024-02-09 07:52:10 +00:00
Sign in to join this conversation.
No description provided.