chat upstreams unreachable in Nomad (#1031) #1032

Merged

dev-qwen merged 2 commits from fix/issue-1031 into main

2026-04-19 04:50:58 +00:00

Author	SHA1	Message	Date
Claude	47046ead2e	fix: add network_mode=host to dispatcher task — FORGE_URL unreachable from bridge namespace All checks were successful ci/woodpecker/push/ci Pipeline was successful Details ci/woodpecker/push/nomad-validate Pipeline was successful Details ci/woodpecker/pr/ci Pipeline was successful Details ci/woodpecker/pr/nomad-validate Pipeline was successful Details ci/woodpecker/pr/secret-scan Pipeline was successful Details The dispatcher task's FORGE_URL was changed to 127.0.0.1:3000 but the task was still in bridge networking mode, making the host's loopback unreachable. Add network_mode = "host" to match the caddy task. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-19 04:44:10 +00:00
Claude	7fd8a0cbba	fix: edge.hcl uses Docker hostname routing — forgejo/woodpecker/chat upstreams unreachable in Nomad (#1031 ) All checks were successful ci/woodpecker/push/ci Pipeline was successful Details ci/woodpecker/push/nomad-validate Pipeline was successful Details ci/woodpecker/pr/ci Pipeline was successful Details ci/woodpecker/pr/nomad-validate Pipeline was successful Details ci/woodpecker/pr/secret-scan Pipeline was successful Details Add network_mode = "host" to the caddy task docker config (matching woodpecker-agent.hcl pattern) and replace all bare Docker hostnames with 127.0.0.1:<port>: - forgejo:3000 → 127.0.0.1:3000 - woodpecker:8000 → 127.0.0.1:8000 - chat:8080 → 127.0.0.1:8080 - FORGE_URL env in both caddy and dispatcher tasks Staging route already uses nomadService discovery (S5-fix-7, #1018). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-19 04:36:32 +00:00