From 7c99dd1aae7912240d6da29ad7434ccada576dbe Mon Sep 17 00:00:00 2001 From: Alexander William Zlotnik Date: Sun, 15 Mar 2026 10:27:15 -0700 Subject: [PATCH] fix: add StartPeriod to storage health check to prevent intermittent failures Storage-api v1.41.8 added a DB connection pool monitor that can delay readiness on startup. Without a StartPeriod, Docker begins counting health check failures immediately, causing the container to be marked unhealthy before it has time to fully initialize (~50% failure rate on ARM CI runners). Adding StartPeriod: 10s gives the storage container a grace window before Docker starts counting failures, matching the pattern already used by Logflare and Mailpit containers. Fixes #4941 --- internal/start/start.go | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/internal/start/start.go b/internal/start/start.go index 53c0032de..98112dc5b 100644 --- a/internal/start/start.go +++ b/internal/start/start.go @@ -1029,9 +1029,10 @@ EOF "CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://127.0.0.1:5000/status", }, - Interval: 10 * time.Second, - Timeout: 2 * time.Second, - Retries: 3, + Interval: 10 * time.Second, + Timeout: 2 * time.Second, + Retries: 3, + StartPeriod: 10 * time.Second, }, }, container.HostConfig{