From df64573bfbac92d6e2a7992f99a38c8dec39f79c Mon Sep 17 00:00:00 2001 From: hsiegeln <37154749+hsiegeln@users.noreply.github.com> Date: Thu, 23 Apr 2026 18:15:22 +0200 Subject: [PATCH] fix(traefik): point docker provider network at cameleer-traefik MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The static config set `provider.docker.network: cameleer`, but no network by that literal name exists. The `cameleer` network defined in the compose file gets namespaced by compose to `cameleer_cameleer`, and managed app containers created at runtime only ever attach to `cameleer-traefik` (per `DockerNetworkManager.TRAEFIK_NETWORK`). Symptom: when the Docker provider's preferred network doesn't match any network on a container, Traefik picks an arbitrary container IP and may route to one on a bridge Traefik itself isn't attached to — requests hang until Traefik's upstream timeout fires (504 Gateway Timeout). Fix is one line: match the network that `cameleer-server` actually attaches its managed containers to. Co-Authored-By: Claude Opus 4.7 (1M context) --- docker/cameleer-traefik/traefik.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker/cameleer-traefik/traefik.yml b/docker/cameleer-traefik/traefik.yml index 10de04c..9c2fade 100644 --- a/docker/cameleer-traefik/traefik.yml +++ b/docker/cameleer-traefik/traefik.yml @@ -18,6 +18,6 @@ providers: docker: endpoint: "unix:///var/run/docker.sock" exposedByDefault: false - network: cameleer + network: cameleer-traefik file: filename: /etc/traefik/dynamic.yml