fix: use host network for API build + full node image #6

Merged

forgejo_admin merged 1 commit from fix-docker-compose-runtime into main

2026-03-17 03:36:41 +00:00

forgejo_admin commented

2026-03-17 03:35:56 +00:00

Contributor

Summary

API build needs network: host to use Tailscale's MagicDNS for PyPI resolution
node:22-alpine crashes during npm install — node:22 (Debian) is stable

Changes

docker-compose.yml: API build uses network: host, app uses node:22 instead of node:22-alpine

Test Plan

docker compose up — all 4 services healthy
API: {"status":"ok","db":"connected"}
App: HTTP 200 at localhost:5173
Keycloak: realm loaded

Review Checklist

No secrets committed
No unnecessary file changes
Commit message is descriptive

Closes #4
plan-mcd-tracker — Phase 7c (Local Dev Stack)

## Summary - API build needs `network: host` to use Tailscale's MagicDNS for PyPI resolution - `node:22-alpine` crashes during npm install — `node:22` (Debian) is stable ## Changes - `docker-compose.yml`: API build uses `network: host`, app uses `node:22` instead of `node:22-alpine` ## Test Plan - [x] `docker compose up` — all 4 services healthy - [x] API: `{"status":"ok","db":"connected"}` - [x] App: HTTP 200 at localhost:5173 - [x] Keycloak: realm loaded ## Review Checklist - [x] No secrets committed - [x] No unnecessary file changes - [x] Commit message is descriptive ## Related - Closes #4 - `plan-mcd-tracker` — Phase 7c (Local Dev Stack)

forgejo_admin added 1 commit

2026-03-17 03:35:56 +00:00

fix: use host network for API build + full node image

ci/woodpecker/pr/woodpecker Pipeline was successful

Details

0ebd323658

Two runtime fixes discovered during first docker compose up:
1. API build needs network: host to resolve DNS through Tailscale's
   MagicDNS (Docker bridge can't reach 100.100.100.100)
2. node:22-alpine crashes with "Exit handler never called" during
   npm install — switch to node:22 (Debian-based, stable)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>