From 6fe623556c579efc1e86b44ec563265de6e74db7 Mon Sep 17 00:00:00 2001 From: archipelago Date: Thu, 9 Jul 2026 19:42:06 -0400 Subject: [PATCH] fix(apps): strfry healthcheck probes 127.0.0.1:7777, not localhost:8090 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The healthcheck runs INSIDE the container, so it must target the container port (7777), not the host mapping (8090) — and 127.0.0.1 explicitly, because `localhost` resolves to ::1 in the image while strfry binds IPv4 0.0.0.0 only. Both bugs verified empirically on .228 (container was Up but "unhealthy"; 127.0.0.1:7777/health returns 200). Ships at the next catalog regen/re-sign (catalog overlay supremacy); with the runtime manifest-reload now in place it will apply fleet-wide on the next catalog refresh, no service restarts needed. Co-Authored-By: Claude Fable 5 --- apps/strfry/manifest.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/apps/strfry/manifest.yml b/apps/strfry/manifest.yml index 301d2492..ef74ed72 100644 --- a/apps/strfry/manifest.yml +++ b/apps/strfry/manifest.yml @@ -198,7 +198,11 @@ app: health_check: type: http - endpoint: http://localhost:8090 + # In-container probe: must target the CONTAINER port (7777), not the host + # mapping (8090), and 127.0.0.1 explicitly — `localhost` resolves to ::1 + # inside the image while strfry binds IPv4 0.0.0.0 only (verified on .228: + # localhost:7777 refused, 127.0.0.1:7777/health = 200). + endpoint: http://127.0.0.1:7777 path: /health interval: 30s timeout: 5s