December 31, 2025Dec 31 Overview: Support for Docker image arch-healarr in the binhex repo.Application: Healarr - https://github.com/binhex/arch-healarrDocker Hub: https://hub.docker.com/r/binhex/arch-healarr/GitHub: https://github.com/binhex/arch-healarrDocumentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here
December 31, 2025Dec 31 Author Hi all, this Docker image is a little different to the rest, namely that i am the author of the app (bash script) and the creator and maintaner of the image, any issues with Healarr app or image please post here.
December 31, 2025Dec 31 I'm seeing an error when installing-[ERROR] 2025-12-31 08:34:00 :: Cannot communicate with Docker daemon, check socket is mounted at /var/run/docker.sockI know the socket is mounted at /var/run/docker.sock because the dockersocket docker is accessing it without any errors.Docker run-docker run -d --name='binhex-healarr' --net='bridge' --pids-limit 2048 -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Brunnhilde" -e HOST_CONTAINERNAME="binhex-healarr" -e 'MONITOR_INTERVAL'='60' -e 'RETRY_COUNT'='3' -e 'RETRY_DELAY'='10' -e 'ACTION'='restart' -e 'CONTAINER_LABEL'='' -e 'CONTAINER_ENV_VAR'='' -e 'CONTAINER_NAME'='' -e 'APPRISE_NOTIFICATION_SERVICES'='' -e 'LOG_LEVEL'='1' -e 'ENABLE_HEALTHCHECK'='yes' -e 'HEALTHCHECK_COMMAND'='' -e 'HEALTHCHECK_ACTION'='' -e 'HEALTHCHECK_HOSTNAME'='cloudflare.com' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/healarr-icon.png' -v '/mnt/cache/appdata/binhex-healarr':'/config':'rw' -v '/var/run/docker.sock':'/var/run/docker.sock':'rw' --restart=always 'ghcr.io/binhex/arch-healarr' 089a08e27682ff770182c8c273aa922c30037b155e58b1f0f535ea39fc225dd1 The command finished successfully!Full log-text error warn system array login Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2025-12-31 08:33:57.936015 [info] Host is running unRAID 2025-12-31 08:33:57.973278 [info] System information: Linux 089a08e27682 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux 2025-12-31 08:33:58.012967 [info] Image architecture: 'amd64' 2025-12-31 08:33:58.040565 [info] Application name: 'healarr' 2025-12-31 08:33:58.065261 [info] Base image release tag: '2025122801' 2025-12-31 08:33:58.089529 [info] Application image release tag: '1.0.14-01' 2025-12-31 08:33:58.122168 [info] PUID defined as '99' 2025-12-31 08:33:58.155451 [info] Executing usermod for PUID '99'... 2025-12-31 08:33:58.250048 [info] usermod completed successfully 2025-12-31 08:33:58.291469 [info] PGID defined as '100' 2025-12-31 08:33:58.333153 [info] Executing groupmod for PGID '100'... 2025-12-31 08:33:58.425479 [info] groupmod completed successfully 2025-12-31 08:33:58.461702 [info] UMASK defined as '000' 2025-12-31 08:33:58.488902 [info] Setting ownership and permissions recursively on '/config'... 2025-12-31 08:33:58.516736 [info] Successfully set ownership and permissions on '/config' 2025-12-31 08:33:58.541706 [info] '/data' directory does not exist, skipping setting (non-recursive) ownership and permissions on '/data' 2025-12-31 08:33:58.588554 [info] Deleting files in /tmp (non recursive)... 2025-12-31 08:33:58.615563 [info] Applying chown to paths '/home/nobody'... 2025-12-31 08:33:58.650138 [info] Starting Supervisor... 2025-12-31 08:33:58,974 INFO Included extra file "/etc/supervisor/conf.d/healarr.conf" during parsing 2025-12-31 08:33:58,975 INFO Set uid to user 0 succeeded 2025-12-31 08:33:58,983 INFO RPC interface 'supervisor' initialized 2025-12-31 08:33:58,984 INFO supervisord started with pid 7 2025-12-31 08:33:59,986 INFO spawned: 'healarr-script' with pid 82 2025-12-31 08:33:59,986 INFO reaped unknown pid 8 (exit status 0) 2025-12-31 08:34:00,022 DEBG 'healarr-script' stdout output: [ERROR] 2025-12-31 08:34:00 :: Cannot communicate with Docker daemon, check socket is mounted at /var/run/docker.sock 2025-12-31 08:34:00,022 INFO success: healarr-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2025-12-31 08:34:00,022 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23405296116336 for <Subprocess at 23405296108272 with name healarr-script in state RUNNING> (stdout)> 2025-12-31 08:34:00,022 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23405295805584 for <Subprocess at 23405296108272 with name healarr-script in state RUNNING> (stderr)> 2025-12-31 08:34:00,023 WARN exited: healarr-script (exit status 1; not expected) 2025-12-31 08:34:00,023 DEBG received SIGCHLD indicating a child quit Edited December 31, 2025Dec 31 by wgstarks
December 31, 2025Dec 31 Author 2 minutes ago, wgstarks said:[ERROR] 2025-12-31 08:34:00 :: Cannot communicate with Docker daemon, check socket is mounted at /var/run/docker.sockHmm interesting!, i had somebody with the exact same issue reported on github (no response back yet), can you try the same:Can you drop to the hosts terminal (not the container) and paste the result of ls -al /var/run/docker.sock also can you tell me what version of unraid you are using.For reference mine looks like this:- srwxrwxrwx 1 root docker 0 Dec 29 11:45 /var/run/docker.sockPlease can you also try going to the containers 'console' and paste the result of docker psEdit - FWIW i am running this with the same PUID and PGID as you and it works, so im unsure as to the cause.
December 31, 2025Dec 31 root@Brunnhilde:~# ls -al /var/run/docker.sock srw-rw---- 1 root docker 0 Dec 23 16:35 /var/run/docker.sock= root@Brunnhilde:~# [root@066ec9412d39 /]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 7beeeae2755d haveagitgat/tdarr "/init" 7 minutes ago Up 7 minutes 0.0.0.0:8264-8266->8264-8266/tcp, [::]:8264-8266->8264-8266/tcp, 8267/tcp tdarr 066ec9412d39 ghcr.io/binhex/arch-healarr "/usr/bin/dumb-init …" 11 minutes ago Up 11 minutes (healthy) binhex-healarr 670c40c0d9e3 binhex/arch-bitmagnet "/usr/bin/dumb-init …" 43 hours ago Up 43 hours (healthy) binhex-bitmagnet a6ef0b7cb477 linuxserver/jackett "/init" 2 days ago Up 2 days jackett 1245e0b74da1 linuxserver/plex "/init" 5 days ago Up 2 days PlexMediaServer a4fdcf865182 stephondoestech/unraid-config-guardian:latest "/entrypoint.sh pyth…" 5 days ago Up 2 days (healthy) 0.0.0.0:7842->7842/tcp, [::]:7842->7842/tcp UnraidConfigGuardian 34fcf433565d 11notes/unifi:10-unraid "/usr/local/bin/entr…" 5 days ago Up 2 days (healthy) 0.0.0.0:1900->1900/udp, [::]:1900->1900/udp, 0.0.0.0:3478->3478/udp, [::]:3478->3478/udp, 0.0.0.0:6789->6789/tcp, [::]:6789->6789/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 0.0.0.0:8443->8443/tcp, [::]:8443->8443/tcp, 0.0.0.0:8843->8843/tcp, [::]:8843->8843/tcp, 0.0.0.0:5514->5514/udp, [::]:5514->5514/udp, 0.0.0.0:10001->10001/udp, [::]:10001->10001/udp, 0.0.0.0:8880->8880/tcp, [::]:8880->8880/tcp unifi-controller-reborn 51cfb3557e9a mbentley/timemachine "/entrypoint.sh s6-s…" 8 days ago Up 2 days TimeMachine_multi b63ad87fb697 linuxserver/mariadb "/init" 12 days ago Up 2 days 0.0.0.0:3306->3306/tcp, [::]:3306->3306/tcp mariadb 9156e34cec56 frooodle/s-pdf:latest "tini -- /scripts/in…" 12 days ago Up 2 days 0.0.0.0:8484->8080/tcp, [::]:8484->8080/tcp StirlingPDF c8e216240e5b ghcr.io/tecnativa/docker-socket-proxy:latest "docker-entrypoint.s…" 12 days ago Up 7 days 2375/tcp dockersocket b5d4dc5c1dc5 binhex/arch-rclone "/usr/bin/dumb-init …" 2 weeks ago Up 2 days (healthy) 0.0.0.0:5572->5572/tcp, [::]:5572->5572/tcp, 0.0.0.0:53682->53682/tcp, [::]:53682->53682/tcp binhex-rclone 109ad0cdb03a mtlynch/picoshare "/app/docker-entrypo…" 3 weeks ago Up 7 days 0.0.0.0:3001->3001/tcp, [::]:3001->3001/tcp picoshare c8be602a238d ghcr.io/cleanuparr/cleanuparr:latest "/entrypoint.sh ./Cl…" 4 weeks ago Up 2 days 0.0.0.0:11011->11011/tcp, [::]:11011->11011/tcp Cleanuparr fa8b0817f943 flaresolverr/flaresolverr "/usr/bin/dumb-init …" 4 weeks ago Up 7 days flaresolverr 41d4f960a440 binhex/arch-prowlarr "/usr/bin/dumb-init …" 4 weeks ago Up 2 days (healthy) binhex-prowlarr 06847a2b4c56 binhex/arch-privoxyvpn "/usr/bin/dumb-init …" 4 weeks ago Up 7 days 0.0.0.0:3333->3333/tcp, [::]:3333->3333/tcp, 0.0.0.0:8118->8118/tcp, [::]:8118->8118/tcp, 0.0.0.0:9117-9118->9117-9118/tcp, [::]:9117-9118->9117-9118/tcp, 0.0.0.0:9696->9696/tcp, [::]:9696->9696/tcp, 0.0.0.0:58946->58946/tcp, [::]:58946->58946/tcp, 0.0.0.0:58946->58946/udp, [::]:58946->58946/udp binhex-privoxyvpn acc82704f01c binhex/arch-qbittorrentvpn "/usr/bin/dumb-init …" 5 weeks ago Up 2 days 0.0.0.0:6881->6881/tcp, [::]:6881->6881/tcp, 0.0.0.0:8088->8088/tcp, 0.0.0.0:6881->6881/udp, [::]:8088->8088/tcp, [::]:6881->6881/udp, 0.0.0.0:8119->8118/tcp, [::]:8119->8118/tcp binhex-qbittorrentvpn 56012c0c391c binhex/arch-radarr "/usr/bin/dumb-init …" 5 weeks ago Up 2 days (healthy) 0.0.0.0:7878->7878/tcp, [::]:7878->7878/tcp binhex-radarr e6cf97f21909 binhex/arch-sonarr "/usr/bin/dumb-init …" 6 weeks ago Up 2 days (healthy) 0.0.0.0:8989->8989/tcp, [::]:8989->8989/tcp, 0.0.0.0:9897->9897/tcp, [::]:9897->9897/tcp binhex-sonarr cbb13a27c8af golift/unpackerr "/unpackerr" 17 months ago Up 7 days unpackerr [root@066ec9412d39 /]#
December 31, 2025Dec 31 20 minutes ago, binhex said:Edit - FWIW i am running this with the same PUID and PGID as you and it works, so im unsure as to the cause.Could the fact that I have another docker using the socket cause this?
December 31, 2025Dec 31 Author Just now, wgstarks said:Could the fact that I have another docker using the socket cause this?Am interesting idea, possibly, try stopping the other container
December 31, 2025Dec 31 24 minutes ago, binhex said:Am interesting idea, possibly, try stopping the other containerDidn’t make any difference. The error is still there.
December 31, 2025Dec 31 Author 10 minutes ago, wgstarks said:Didn’t make any difference. The error is still there.ok ive created a new image, pull when you can, i have split the detection of the socket and the check for the daemon (performs docker ps ) so it may help work out what the issue is, let me know what the logs say.
December 31, 2025Dec 31 27 minutes ago, binhex said:ok ive created a new image, pull when you can, i have split the detection of the socket and the check for the daemon (performs docker ps ) so it may help work out what the issue is, let me know what the logs say.[ERROR] 2025-12-31 10:26:49 :: Cannot communicate with Docker daemon ('docker ps' returned non zero exit code '0'), exiting script...Supervisord.log-Created by...___. .__ .__\_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/2025-12-31 10:26:47.703811 [info] Host is running unRAID2025-12-31 10:26:47.736078 [info] System information: Linux d729842a65bd 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux2025-12-31 10:26:47.764081 [info] Image architecture: 'amd64'2025-12-31 10:26:47.791423 [info] Application name: 'healarr'2025-12-31 10:26:47.822162 [info] Base image release tag: '2025122801'2025-12-31 10:26:47.846505 [info] Application image release tag: '1.0.16-01'2025-12-31 10:26:47.877058 [info] PUID defined as '99'2025-12-31 10:26:47.911969 [info] Executing usermod for PUID '99'...2025-12-31 10:26:47.971317 [info] usermod completed successfully2025-12-31 10:26:48.000254 [info] PGID defined as '100'2025-12-31 10:26:48.027378 [info] Executing groupmod for PGID '100'...2025-12-31 10:26:48.113428 [info] groupmod completed successfully2025-12-31 10:26:48.136363 [info] UMASK defined as '000'2025-12-31 10:26:48.162172 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'2025-12-31 10:26:48.220284 [info] Deleting files in /tmp (non recursive)...2025-12-31 10:26:48.247372 [info] Applying chown to paths '/home/nobody'...2025-12-31 10:26:48.281324 [info] Starting Supervisor...2025-12-31 10:26:48,553 INFO Included extra file "/etc/supervisor/conf.d/healarr.conf" during parsing2025-12-31 10:26:48,553 INFO Set uid to user 0 succeeded2025-12-31 10:26:48,557 INFO RPC interface 'supervisor' initialized2025-12-31 10:26:48,558 INFO supervisord started with pid 72025-12-31 10:26:49,560 INFO spawned: 'healarr-script' with pid 762025-12-31 10:26:49,560 INFO reaped unknown pid 8 (exit status 0)2025-12-31 10:26:49,596 DEBG 'healarr-script' stdout output:[ERROR] 2025-12-31 10:26:49 :: Cannot communicate with Docker daemon ('docker ps' returned non zero exit code '0'), exiting script...2025-12-31 10:26:49,596 INFO success: healarr-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)2025-12-31 10:26:49,596 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23090544910960 for <Subprocess at 23090544902896 with name healarr-script in state RUNNING> (stdout)>2025-12-31 10:26:49,596 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23090544600208 for <Subprocess at 23090544902896 with name healarr-script in state RUNNING> (stderr)>2025-12-31 10:26:49,596 WARN exited: healarr-script (exit status 1; not expected)2025-12-31 10:26:49,596 DEBG received SIGCHLD indicating a child quit
December 31, 2025Dec 31 Author 3 hours ago, wgstarks said:srw-rw---- 1 root docker 0 Dec 23 16:35 /var/run/docker.sock=i know what's going on!, so i had totally forgotten that i modified permissions to the docker socket as a pre-startup script for code-server (another awesome image), and that's why it worked for me and not you, these are the permissions i see:srwxrwxrwx 1 root docker 0 Dec 29 11:45 /var/run/docker.sockso as you can see you have only read and write for user root (srw-rw----), group docker, which PUID 99 (nbody) and PGID 100 (users) has no access to, whereas i have rwx for user root, group docker and everyone.This grants me full permissions for 'everyone' which obviously includes user 'nobody'. So i know what the fix is and i have put it in the image please pull down at your convieniece, it does mean it will modify your permissions to permit read and write for the docker socker for everyone, the alternative is to run this image as user root, neither are ideal tbh, but i think setting permissions on the socket is preferable.
December 31, 2025Dec 31 Author I've come up with a better solution, edit the group for user nobody to match the docker sockets GID (281 in the case of unraid), its more secure and does not change permissions for the socket, please pull down image at your convienience.
December 31, 2025Dec 31 If I don’t set any container filters will this docker just monitor all containers?
December 31, 2025Dec 31 10 minutes ago, wgstarks said:If I don’t set any container filters will this docker just monitor all containers?Nevermind, found it in the logs “no filters specified monitoring all containers”.
April 3Apr 3 I'm also having problems where none of my containers restart. Thanks for any guidance you can provide. My hunch is my permissions on the docker.sock need to be updated to allow r/w access to user:nobody? Based on the prior questions, here are some details:root@unRAID:~# ls -al /var/run/docker.socksrw-rw---- 1 root docker 0 Mar 24 07:48 /var/run/docker.sock=docker run -d --name='binhex-healarr' --net='bridge' --pids-limit 2048 -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="unRAID" -e HOST_CONTAINERNAME="binhex-healarr" -e 'DOCKER_HOST'='' -e 'MONITOR_INTERVAL'='60' -e 'RETRY_COUNT'='3' -e 'RETRY_DELAY'='10' -e 'ACTION'='restart' -e 'CONTAINER_LABEL'='' -e 'CONTAINER_ENV_VAR'='MONITOR_ENABLED=true' -e 'CONTAINER_NAME'='' -e 'APPRISE_NOTIFICATION_SERVICES'='' -e 'LOG_LEVEL'='1' -e 'ENABLE_HEALTHCHECK'='yes' -e 'HEALTHCHECK_COMMAND'='' -e 'HEALTHCHECK_ACTION'='' -e 'HEALTHCHECK_HOSTNAME'='google.com' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/healarr-icon.png' -v '/mnt/user/appdata/binhex-healarr':'/config':'rw' -v '/var/run/docker.sock':'/var/run/docker.sock':'rw' --restart=always 'ghcr.io/binhex/arch-healarr'Created by...___. .__ .__\_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/2026-04-03 08:32:15.249214 [info] Host is running unRAID2026-04-03 08:32:15.269035 [info] System information: Linux ea450202c871 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux2026-04-03 08:32:15.289080 [info] Image architecture: 'amd64'2026-04-03 08:32:15.307815 [info] Application name: 'healarr'2026-04-03 08:32:15.327875 [info] Base image release tag: '2025122801'2026-04-03 08:32:15.347837 [info] Application image release tag: '1.0.25-01'2026-04-03 08:32:15.371331 [info] PUID defined as '99'2026-04-03 08:32:15.398007 [info] Executing usermod for PUID '99'...2026-04-03 08:32:15.433845 [info] usermod completed successfully2026-04-03 08:32:15.457512 [info] PGID defined as '100'2026-04-03 08:32:15.479901 [info] Executing groupmod for PGID '100'...2026-04-03 08:32:15.518542 [info] groupmod completed successfully2026-04-03 08:32:15.538752 [info] UMASK defined as '000'2026-04-03 08:32:15.562347 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'2026-04-03 08:32:15.589881 [info] Deleting files in /tmp (non recursive)...2026-04-03 08:32:15.651967 [info] Applying chown to paths '/home/nobody'...2026-04-03 08:32:15.681156 [info] Starting Supervisor...2026-04-03 08:32:15,800 INFO Included extra file "/etc/supervisor/conf.d/healarr.conf" during parsing2026-04-03 08:32:15,800 INFO Set uid to user 0 succeeded2026-04-03 08:32:15,803 INFO RPC interface 'supervisor' initialized2026-04-03 08:32:15,804 INFO supervisord started with pid 72026-04-03 08:32:16,806 INFO spawned: 'healarr-script' with pid 812026-04-03 08:32:16,807 INFO reaped unknown pid 8 (exit status 0)2026-04-03 08:32:16,859 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: Docker socket at '/var/run/docker.sock' is accessible2026-04-03 08:32:16,859 INFO success: healarr-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)2026-04-03 08:32:16,862 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: Docker CLI and Apprise CLI found and accessible2026-04-03 08:32:16,866 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: MONITOR_INTERVAL set to '60' seconds2026-04-03 08:32:16,870 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: RETRY_COUNT set to '3'2026-04-03 08:32:16,874 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: RETRY_DELAY set to '10' seconds2026-04-03 08:32:16,879 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: ACTION set to 'restart'2026-04-03 08:32:16,883 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: Filtering containers by environment variable: MONITOR_ENABLED=true2026-04-03 08:32:16,887 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: Starting healarr (interval: 60 seconds)...2026-04-03 08:32:16,931 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: Healarr self-health check passed (status: starting). Proceeding with container monitoring...2026-04-03 08:32:16,950 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: No unhealthy containers found2026-04-03 08:32:16,955 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:32:16 :: Sleeping for 60 seconds before next check...2026-04-03 08:33:17,001 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:33:16 :: Healarr self-health check passed (status: healthy). Proceeding with container monitoring...2026-04-03 08:33:17,023 DEBG 'healarr-script' stdout output:[INFO] 2026-04-03 08:33:17 :: No unhealthy containers found
April 3Apr 3 Author 8 hours ago, Kash76 said: -e 'CONTAINER_ENV_VAR'='MONITOR_ENABLED=true'i see you have set the containers to monitor based on env var, so only containers that have the specified env var set, so for you that is key name 'MONITOR_ENABLED' and value 'true', so have you set that env var for prowlarr and gluetun containers?, also please do note healarr will only monitor containers that include health checks (all of the images i produce do), so looking at your screenshot only prowlarr and gluetun container have healthchecks so at best only these two will be rebooted dependant on the env var being set for the container (as previously mentioned) and the health being 'unhealthy'.
April 5Apr 5 Ah! Only your containers since you have the health check. Thank you!! I have converted to your containers. I really appreciate the help!!
April 5Apr 5 Author 15 hours ago, Kash76 said:Ah! Only your containers since you have the health checkJust to be clear, you don't have to use ONLY my images, other images from other developers MAY also incude health checks, for instance gluetun does, by looks of your screenshot it appears linuxserver does not, which is a little surprising.
April 5Apr 5 1 hour ago, binhex said:Just to be clear, you don't have to use ONLY my images, other images from other developers MAY also incude health checks, for instance gluetun does, by looks of your screenshot it appears linuxserver does not, which is a little surprising.good that you remind me, your delugevpn image is lacking the healthcheck^^
June 8Jun 8 Author 3 hours ago, john_smith said:does healarr support self-hosted ntfy notifications ?right now, nope.Actually i have not drunk enough coffee!, it doesnt specify ntfy directly, its using the excellent apprise tool, so yep it will support local or cloud ntfy services: https://appriseit.com/services/ntfy/#syntax
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.