From 1251896a42a75e9587af3120d79d9d76db523c09 Mon Sep 17 00:00:00 2001
From: Jack Spiering <46534141+jackspiering@users.noreply.github.com>
Date: Mon, 8 Jun 2026 16:44:17 +0200
Subject: [PATCH] Remove healthcheck from Portainer service

The Portainer health check is being removed because the official portainer/portainer-ce image is a minimal scratch-based image that does not include common utilities such as wget, curl, nc, or pgrep.

As a result, meaningful Docker health checks cannot be implemented reliably without switching to a different image variant. Since the container already uses restart: always, Docker will continue to restart Portainer if the process exits.

Users who require availability monitoring are encouraged to use an external monitoring solution such as Uptime Kuma.

This will fix #305
---
 services/portainer/compose.yaml | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/services/portainer/compose.yaml b/services/portainer/compose.yaml
index 917fbc1f..a173f821 100644
--- a/services/portainer/compose.yaml
+++ b/services/portainer/compose.yaml
@@ -62,10 +62,4 @@ services:
     depends_on:
       tailscale:
         condition: service_healthy
-    healthcheck:
-      test: ["CMD", "pgrep", "-f", "${SERVICE}"] # Check if ${SERVICE} process is running
-      interval: 1m # How often to perform the check
-      timeout: 10s # Time to wait for the check to succeed
-      retries: 3 # Number of retries before marking as unhealthy
-      start_period: 30s # Time to wait before starting health checks
     restart: always