df64573bfbac92d6e2a7992f99a38c8dec39f79c
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) <noreply@anthropic.com>
Description
Multi-tenant SaaS platform — Camel application runtime with built-in observability. Wraps cameleer3 agent + server.
Languages
Java
47.4%
TypeScript
23.4%
Shell
16.5%
PowerShell
11.3%
Dockerfile
0.7%
Other
0.7%