HEALTHCHECK start period may be insufficient for slow networks

[robocopklaus]

Description

The HEALTHCHECK is configured with a 5-second start period. While Blocky downloads blocklists asynchronously (so DNS service starts quickly), very slow networks may still cause the health check to fail during initial startup.

File(s)

• blocky/Dockerfile (lines 91-92)

Evidence

HEALTHCHECK --interval=30s --timeout=10s --start-period=5s --retries=3 \
    CMD blocky blocking status || exit 1

Recommendation

Consider increasing --start-period to 30s for robustness on constrained devices. Document expected startup time for users with large blocklists.

Risk if Ignored

On first deployment with slow networks, health checks may fail during initialization, causing unnecessary container restarts.

---

Found by: Dockerfile & Container Specialist (Agent 1) | Reviewed by: Critique Agent — downgraded from INFO (Blocky downloads lists asynchronously)