wgstarks

That fixed it.👍

[ERROR] 2025-12-31 10:26:49 :: Cannot communicate with Docker daemon ('docker ps' returned non zero exit code '0'), exiting script... Supervisord.log-

Didn’t make any difference. The error is still there.

Could the fact that I have another docker using the socket cause this?

unRaid=7.2.3

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 /]#

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.sock I 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

It will work on an external drive but sometimes USB drives will disconnect randomly so it’s likely better to have the files on the array. Both are options though and you’ll likely want to experiment with your setup to see what works best for you.

Yes, you can use UD to mount an external drive on your Unraid server. I’m not sure what you are planning after that? Are you moving the Plex app to a docker on Unraid? Transferring the data on the USB drive to the array or a pool?

Neat trick.👍 I see that many variables have been added. Is there a way to update my template without losing my current db? I know I can manually add the variables but really didn’t want to have to type out all the descriptions.

Is there a variable to limit how many backups are retained? I think they’re a good idea but don’t need to keep an infinite number. Checked GitHub but don’t see any of these variables listed there.

@PeteAsking Just updated using method 1 but ran into a few issues. They were completely my own fault but could be avoided with a small edit. When reconfiguring I copy/pasted the repo field shown below. This resulted in some invalid spaces and several failed installs. Perhaps you could edit the post to add a code line that will paste without errors?

I haven’t had any issues with backups to this docker but decided to test your recommended settings anyway. It’s hard to really do a good comparison of multiple backups but my typical backup takes ~20 minutes. This one took less than 5 minutes. I think I’ll keep the changes for a while.

I can’t say for sure if this will fix your issue but over the years it has fixed mine multiple times. Have you tried a full Recovery install of macOS?

What is your host path and container path for host path 3?

Please describe what path you are trying to configure (include screenshots) as well as the error you get.

Any directory added at the root would be a new share. You must add shares from the webUI.

Remember you can activate the help menu on any page by clicking the question mark.

High water calculates the amount of free space available for each drive and will then fill the drive with the most free space until it has used half that space. If the drive has 8TB free it will write to the drive until there is only 4TB free. However, your split level setting overrides the allocation method. If your split level setting is too restrictive then allocation is ignored and Unraid will continue to write to the same drive. Be sure split level is set to “Automatically split any directory as required” to prevent this. It also may be that if you move a bunch of data in one big transfer, that write will continue until completion without re-calculating high water. Just a guess on my part though. Perhaps @trurl can comment on that? In regards to Plex I would suggest seeking help in the Plex forum. You may also be able to get help in the support thread for whichever Plex docker you installed. They should all have a dedicated support thread you can access by clicking the docker’s icon and selecting “support”.

What split level are you using?

Once the high water mark is reached on the current drive it will be recalculated and the new high water mark will be used on the drive with the most free space. You can see full descriptions of the various settings by clicking the question mark ?

The Unraid Docs I linked in my last post describes this all in order step-by-step.

Check out Unraid Docs. It’s a little dated since I don’t believe it has any info about zfs pools but it has a very good step-by-step for the initial Unraid setup along with terminology and descriptions.

Doesn’t Windows Server have access to the SMB network? SMB will likely be much slower than a direct USB or SATA connection but it is an option. You just need to configure SMB sharing in the user share settings for the share you want to transfer the files to. Using the Unassigned Devices plugin you can also mount a Windows Server share in Unraid to transfer the files.

So Unraid no longer supports caching outside of pools? Or maybe it’s an “If it ain’t broke don’t fix it” situation and removing the pool won’t really change anything?