From d54107d7229cc085f4a6806058eeb7534893964b Mon Sep 17 00:00:00 2001 From: ogrechko Date: Wed, 9 Sep 2026 06:42:45 +0000 Subject: [PATCH] Pin an explicit Docker network subnet MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Docker's auto-assigned default bridge range can land on the same block as a real LAN/VLAN on the host it's deployed to, breaking routing to that network. Same fix already applied to zportal (10.199.0.0/24) and kkpab (10.200.0.0/24); this one takes 10.201.0.0/24. Not applied to the currently running deployment on this host (no `docker compose up -d` run here) — takes effect on the next redeploy or on a fresh clone. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01Gh2UXUQUVBWroWEnn1FLFG --- docker-compose.yml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docker-compose.yml b/docker-compose.yml index 156dd03..05899a6 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -16,6 +16,21 @@ services: volumes: - data:/data restart: unless-stopped + networks: + top_tickets_net: + ipv4_address: 10.201.0.10 volumes: data: + +# Explicit subnet — Docker's auto-assigned default bridge range (often +# 172.17-172.31.0.0/16) can land on the same block as a real LAN/VLAN, +# breaking routing to it from this host. Picking a private range nothing +# else here uses avoids that; see zportal (10.199.0.0/24) and kkpab +# (10.200.0.0/24) for the same pattern. +networks: + top_tickets_net: + driver: bridge + ipam: + config: + - subnet: 10.201.0.0/24