switchboard/core
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Releases 9 Wiki Activity

Fix CI DinD networking: host network mode + curl timeout
Some checks failed
CI/CD / detect-changes (pull_request) Successful in 3s
Details
CI/CD / test-frontend (pull_request) Successful in 6s
Details
CI/CD / test-go-pg (pull_request) Successful in 2m43s
Details
CI/CD / test-sqlite (pull_request) Successful in 2m49s
Details
CI/CD / test-runners (pull_request) Failing after 38s
Details
CI/CD / build-and-deploy (pull_request) Has been skipped
Details

Browse Source 
The previous fix (container IP resolution) still failed because the
CI runner and compose containers are on separate Docker networks.

- Add docker-compose.ci.yml override with network_mode: host so the
  container shares the runner's network stack directly
- Add --connect-timeout 2 to curl in wait-for-healthy.sh so it fails
  fast instead of hanging indefinitely on unreachable hosts
- Cap health check at 30s (server boots in 5-10s)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jeffrey Smith
2026-04-02 09:09:06 +00:00
parent 4a4160300b
commit e45c31caaa
3 changed files with 14 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docker-compose.ci.yml Normal file
View File

@@ -0,0 +1,7 @@
# CI override — uses host networking so the container is reachable
# from the Gitea runner pod without cross-network routing.
#
# Usage: docker compose -f docker-compose.yml -f docker-compose.ci.yml up -d
services:
armature:
network_mode: host