Some checks failed
Release - Northern Thailand Ping River Monitor / Create Release (push) Successful in 6s
Security & Dependency Updates / Dependency Security Scan (push) Successful in 26s
Security & Dependency Updates / License Compliance (push) Successful in 11s
Release - Northern Thailand Ping River Monitor / Test Release Build (3.12) (push) Successful in 17s
Release - Northern Thailand Ping River Monitor / Build Release Images (push) Successful in 6m9s
Release - Northern Thailand Ping River Monitor / Security Scan (push) Successful in 7s
Release - Northern Thailand Ping River Monitor / Test Release Deployment (push) Failing after 1m23s
Release - Northern Thailand Ping River Monitor / Notify Release (push) Successful in 1s
Security & Dependency Updates / Check for Dependency Updates (push) Successful in 20s
Security & Dependency Updates / Code Quality Metrics (push) Successful in 16s
Release - Northern Thailand Ping River Monitor / Test Release Build (3.10) (push) Successful in 15s
Release - Northern Thailand Ping River Monitor / Test Release Build (3.11) (push) Successful in 13s
Release - Northern Thailand Ping River Monitor / Test Release Build (3.9) (push) Successful in 15s
Security & Dependency Updates / Security Summary (push) Successful in 7s
Root Cause Identified: - Gitea runner runs inside docker.gitea.com/runner-images:ubuntu-latest - App container runs as sibling container, not accessible via localhost:8080 - Port mapping works for host access, but not container-to-container Networking Solution: - Get container IP with: docker inspect ping-river-monitor-test - Connect directly to container IP:8000 (internal port) - Fallback to localhost:8080 if IP detection fails - Bypasses localhost networking issues in containerized CI Updated Health Checks: - Use container IP for direct communication - Test internal port 8000 instead of mapped port 8080 - More reliable in containerized CI environments - Better debugging with container IP logging Should resolve curl connection failures in Gitea CI environment