grabowski
4336e99e0c
Some checks failed
Release - Northern Thailand Ping River Monitor / Create Release (push) Failing after 17s
Release - Northern Thailand Ping River Monitor / Test Release Build (3.10) (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Test Release Build (3.11) (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Test Release Build (3.12) (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Test Release Build (3.9) (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Build Release Images (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Security Scan (push) Has been skipped
Release - Northern Thailand Ping River Monitor / Test Release Deployment (push) Has been skipped
Security & Dependency Updates / Dependency Security Scan (push) Successful in 2m9s
Security & Dependency Updates / License Compliance (push) Successful in 15s
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 / Notify Release (push) Successful in 1s
Security & Dependency Updates / Security Summary (push) Successful in 7s
Brilliant Solution Implemented: - Create dedicated Docker network (ci_net) for container communication - Use container name resolution (ping-river-monitor-test:8000) - Separate curl container for probing (curlimages/curl:8.10.1) - Clean separation of concerns and reliable networking Key Improvements: - set -euo pipefail for strict error handling - Container name resolution instead of IP detection - Dedicated curl container on same network - Cleaner probe() function for reusability - Better error messages and debugging Network Architecture: 1. ci_net: Custom Docker network 2. ping-river-monitor-test: App container on ci_net 3. curlimages/curl: Probe container on ci_net (ephemeral) 4. Direct container-to-container communication Fallback Strategy: - Primary: Container name resolution on ci_net - Fallback: Host gateway probing via published port - Comprehensive coverage of networking scenarios This should definitively resolve all networking issues!