DarylJ

Yes it is. Edit: To be clear, everything is running just fine. The only issue I'm aware of is the container being marked unhealthy. Oh, portainer just gave me more information: Health check exceeded timeout (30s): [info] So yeah, it's taking 37 seconds to finish the check on average. sh-5.3# date Thu 7 Aug 12:09:49 EDT 2025 sh-5.3# healthcheck.sh [info] No custom healthcheck command defined via env var 'HEALTHCHECK_COMMAND', running default healthchecks... [info] Health checking DNS... [info] DNS resolution is working. [info] Health checking HTTPS... [info] HTTPS request is working. [info] Health checking processes... [info] Application name is 'sonarr'. [info] Process 'Sonarr' is running. [info] Healthcheck passed, exiting script with exit code '0' sh-5.3# date Thu 7 Aug 12:10:26 EDT 2025

Thanks for the reply. Unfortunately that didn't lead me to anything obvious: sh-5.3# healthcheck.sh [info] No custom healthcheck command defined via env var 'HEALTHCHECK_COMMAND', running default healthchecks... [info] Health checking DNS... [info] DNS resolution is working. [info] Health checking HTTPS... [info] HTTPS request is working. [info] Health checking processes... [info] Application name is 'sonarr'. [info] Process 'Sonarr' is running. [info] Healthcheck passed, exiting script with exit code '0'

Is anyone else seeing all of these binhex-*arr continers now failing healthchecks and showing as "unhealthy" since the update 4 days ago?