v0.292.0: cloudflared readiness health check (R-841) — tunnel --metrics localhost:20241 run + Docker healthcheck on cloudflared's own /ready; the host agent reports running/not_running/unknown from State.Health

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-10-04 13:16:26 +02:00
parent badc9c2a0c
commit 09e634de31
6 changed files with 55 additions and 10 deletions
@@ -6,7 +6,17 @@ services:
    image: {{.Image}}
    container_name: cloudflared
    restart: unless-stopped
-    command: tunnel run
+    # R-841: metrics on the container's own loopback at a FIXED port, and a health check that asks cloudflared itself
+    # whether the tunnel is CONNECTED (`/ready`: 200 with readyConnections > 0, else 503 — measured 2026-10-04: with a
+    # wrong token the container stays "running" while /ready is 503). The host agent reads the result with
+    # `docker inspect` (State.Health) and reports the tunnel as running | not_running | unknown.
+    command: tunnel --metrics localhost:20241 run
+    healthcheck:
+      test: ["CMD", "cloudflared", "tunnel", "--metrics", "localhost:20241", "ready"]
+      interval: 30s
+      timeout: 10s
+      retries: 3
+      start_period: 30s
    environment:
      - TUNNEL_TOKEN={{.CFTunnelToken}}
    dns: