From b17807faa3ff0132fe050a4446dddf98a2e58211 Mon Sep 17 00:00:00 2001 From: Kevin Veen-Birkenbach Date: Tue, 27 Oct 2026 13:35:30 +0100 Subject: [PATCH] fix(web-app-nextcloud): probe the Context Agent without curl Context Agent 2.10.0 (bumped in #1219) moved to a multi-stage image whose runtime stage ships no curl ("no vim, no git, no curl, no pipx/poetry", nextcloud/context_agent Dockerfile at v2.10.0). The curl healthcheck then fails with `exec: "curl": executable file not found in $PATH`, the task never leaves `starting`, and the swarm converge wait gives up on nextcloud_context_agent (main run 40401200083, Nextcloud#2). Switch to the http_status flavor, which speaks HTTP over bash's /dev/tcp and still requires a 2xx/3xx answer from /heartbeat. Co-Authored-By: Claude Opus 5.5 --- roles/web-app-nextcloud/meta/services.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/web-app-nextcloud/meta/services.yml b/roles/web-app-nextcloud/meta/services.yml index 1e35ea097a..eabc21d99a 100644 --- a/roles/web-app-nextcloud/meta/services.yml +++ b/roles/web-app-nextcloud/meta/services.yml @@ -155,7 +155,7 @@ context_agent: internal: http: 23000 healthcheck: - flavor: curl + flavor: http_status path: heartbeat # nocheck: healthcheck-timing-override a sidecar of a stack whose main service alone takes minutes; the value predates this default and has not been measured against it start_period: 20m