fix: use api-proxy IP address instead of hostname for BASE_URL

[Claude]

Codex was unable to connect to the api-proxy sidecar due to DNS resolution failures when using the hostname api-proxy.

Changes

• src/docker-manager.ts: Configure OPENAI_BASE_URL and ANTHROPIC_BASE_URL to use the api-proxy IP address (172.30.0.30) instead of hostname
• src/types.ts: Update documentation to reflect IP-based endpoints
• src/docker-manager.test.ts: Update test assertions to expect IP addresses

Example

Before:

environment.OPENAI_BASE_URL = `http://api-proxy:10000`;
environment.ANTHROPIC_BASE_URL = `http://api-proxy:10001`;

After:

environment.OPENAI_BASE_URL = `http://${networkConfig.proxyIp}:10000`;  // 172.30.0.30
environment.ANTHROPIC_BASE_URL = `http://${networkConfig.proxyIp}:10001`;

The api-proxy container retains its static IP assignment on the Docker network. This change only affects how the agent container's environment variables are configured.

[Copilot]

Pull request overview

This PR fixes DNS resolution failures when connecting to the api-proxy sidecar by changing the BASE_URL environment variables to use the IP address (172.30.0.30) instead of the hostname (api-proxy). This ensures reliable connectivity between the agent container and the api-proxy sidecar, particularly during container startup when DNS resolution may not yet be reliable.

Changes:

• Updated BASE_URL configuration to use IP addresses instead of hostnames for api-proxy connections
• Updated documentation to reflect the IP-based endpoint pattern
• Updated test assertions to expect IP addresses in the generated configuration

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/types.ts	Updated documentation comments to show IP-based endpoints (172.30.0.30) instead of hostname-based endpoints
src/docker-manager.ts	Changed OPENAI_BASE_URL and ANTHROPIC_BASE_URL to use networkConfig.proxyIp variable, added explanatory comment
src/docker-manager.test.ts	Updated all test expectations to verify IP-based URLs instead of hostname-based URLs

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

While using IP addresses fixes the immediate DNS resolution issue, there's a related problem in the iptables setup script. The setup-iptables.sh script (lines 134-148) still uses getent hosts api-proxy to resolve the IP address for NAT rules, which could fail with the same DNS resolution issue. Consider updating that script to use the AWF_API_PROXY_IP environment variable instead, which is already being passed and contains the correct IP address. This would provide a more complete fix and ensure consistency across the entire networking setup.