Docker Network Architecture on linuxserver.lan
Traffic flows through network layers from external access to internal services:
These 5 networks form the backbone of the infrastructure. Most services connect to multiple core networks.
traefik-netAll externally accessible services. Traefik routes HTTPS traffic to containers on this network.
Connected: 40+ containerskeycloak-netOAuth2 proxies connect here to validate tokens with Keycloak. Essential for SSO.
Connected: 21 containerspostgres-netPostgreSQL database connectivity. Services needing relational data connect here.
Connected: 16 containersmcp-netModel Context Protocol servers communicate here. Central to AI agent operations.
Connected: 18 containersloki-netLog aggregation network. Promtail sends logs to Loki; Grafana queries Loki.
Connected: 5 containersStandard patterns for connecting containers to networks based on service type:
Used for services requiring SSO protection and external access.
Examples: Grafana, Portainer, Dozzle
Used for services that need external access and database connectivity.
Examples: Keycloak, LiteLLM, n8n
Used for standalone services with only external access needs.
Examples: Draw.io, Stirling PDF, Bitwarden
Used for MCP servers that need tool access and inter-server communication.
Examples: mcp-postgres (mcp-net + postgres-net), mcp-filesystem (mcp-net only)