Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit 26c0a9d

Browse files
eiler2005claude
andcommitted
fix: channel-m extra_hosts requires explicit gateway IP, not host-gateway
host-gateway resolves to 172.17.0.1 (docker0) but the Channel M reverse tunnel binds on the deploy_default network gateway (172.18.0.1). Use MAX_EGRESS_PROXY_GATEWAY from deploy/.env (written by 23-channel-m-reverse.yml) so the extra_hosts mapping points at the correct docker bridge listener. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 1b9dd30 commit 26c0a9d

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

‎deploy/docker-compose.prod.yml‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,10 @@ services:
1515
STARTUP_TESTS_ENABLED: "1"
1616
STARTUP_TESTS_TIMEOUT_SECONDS: "120"
1717
extra_hosts:
18+
# MAX_EGRESS_PROXY_HOST and MAX_EGRESS_PROXY_GATEWAY are set in
19+
# deploy/.env by 23-channel-m-reverse.yml. Defaults are no-ops when
20+
# Channel M is not deployed. host-gateway is wrong here because the
21+
# tunnel binds on the deploy_default network gateway, not docker0.
1822
- "${MAX_EGRESS_PROXY_HOST:-channel-m.invalid}:${MAX_EGRESS_PROXY_GATEWAY:-host-gateway}"
1923
user: "${APP_UID:-1000}:${APP_GID:-1000}"
2024
restart: always

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /