sjtuross

Is it possible to have docker daemon start complete trigger? My script depends on some docker network interfaces which only become available after docker daemon starts.

array_start_complete works as expected. Thank you!

Thanks for the quick response. Yes, in my case, it's the other way around because I want to merge some cloud drives which are mounted by a container. Do you happen to know if the "At Startup of Array" event in the "User Scripts" plugin would block array start?

I put some script in /etc/mergerfsp/array_start.sh to wait a container ready before running mergerfs. It blocks array start forever because docker won't start until array is started. Is it possible to run this array_start.sh asynchronously?

Can we have an option to disable Docker update check for all? It shouldn't be warning, but notice at most.

It can show the network name correctly in the past, at least when I upgraded to Unraid 6.12.0. Not sure when and why it started showing network id only. Everything works, but it just looks odd.

Thanks for this plugin. Do you think if the tools from https://github.com/trapexit/mergerfs-tools can be packaged together?

Is there a way to disable the autostart order check feature? I want to keep the order of my folders and containers as I like and don't care whether it aligns to the actual auto start order. However, I don't want to see a red "autostart order" icon in the top-right toolbar.

Thank you for maintaining this wonderful plugin. I really appreciate it. It works great so far. Just a small ask. Would it be possible to add some indent for containers shown under a folder? Also make the folder name bold and its icon a bit larger, like the below from the old one. When folders are expanded, I feel it's more obvious to tell the difference between folder vs. container.

I don't think this is possible to config in unraid, but you could achieve that through firewall rule in your router.

Before 6.12, nginx, samba such services listen on 0.0.0.0, so I changed rc.nginx to listen on the interface configured IP. Check "Network Improvements" from https://unraid.net/blog/6-12-0-stable. You can now include/exclude listening interfaces. Also the services now listen on IP address of each interface rather than 0.0.0.0

I updated the gist for 6.11.5 with very minor change. You can also compare it with the original file to see what's changed. It should work. This is no longer needed since 6.12 because management services listen on specific IP addresses by default.

In the recent update, orphaned image is now automatically removed. Thank you. Is it possible to also update the local sha256 hash in this file /var/lib/docker/unraid-update-status.json? Since local sha256 is different from remote sha256 there, dockerman keeps showing update ready until I manually update the local sha256 hash. "library/traefik:latest": { "local": "sha256:2e53e47b59bc9a799b6c7b0d6d65f529de478094781751f1e061516ce9ca7c68", "remote": "sha256:ac1480ce3203541705b01d6dce40ef4bf563cdb29d5b00db88cc396fa9fa9cd5", "status": "true" }

Every time after I update stack for new images, I need to do 2 extra steps below. Could this be automated so its behavior is more integrated with Unraid dockerman? Manually remove orphaned image. Manually update image local digest in /var/lib/docker/unraid-update-status.json (taking traefik as an example), so Unraid dockerman stops saying update ready. "library/traefik:latest": { "local": "sha256:4c388f477f5b7aa48420694d90db0ecb96b4ecede60b9b7589c87858abf87b60", "remote": "sha256:4c388f477f5b7aa48420694d90db0ecb96b4ecede60b9b7589c87858abf87b60", "status": "true" }

I run `docker images --digests --no-trunc` and found out the same image with 2 different digests. Most probably the same image was republished to docker hub. So I deleted the image, restart the stack and then click "check for updates" in webui. Now it says up-to-date. It's a false alarm to docker compose manager which is awesome.