October 11, 20232 yr Version 6.12.4. Like many people, I need some containers to wait for others before starting up to avoid issues. So I put them in order, and I did some delays. My understanding is that they'd boot top-down, and delay when they hit a delay. But as you can see from my delays and uptimes, that definitely isn't happening. Can someone explain what I'm doing wrong here?
October 11, 20232 yr When you first start the array, go to the docker tab and see if it's running through the auto start sequence. Set a long wait (maybe 300 seconds?) on the first container in the list. Until you get this figured out I'd disable auto start on all but the first 4 containers so you can start things correctly.
October 11, 20232 yr Author OK, I don't restart the array all THAT often. I was basing my complaint on my stopping all containers and then hitting the 'start all' button. Is that...incorrect?
October 12, 20232 yr 1 hour ago, Merijeek said: OK, I don't restart the array all THAT often. I was basing my complaint on my stopping all containers and then hitting the 'start all' button. Is that...incorrect? The order and delay only applies to array start. Start all means exactly that, start all the containers. Auto start refers to containers you want started without manual intervention when the array starts. Currently there is no mechanism in place to recreate array start conditions for the list of containers without actually stopping and starting the array. It's pretty easy to write a script to start containers, so if you regularly stop all your containers without stopping the array I'd recommend just scripting it. docker start <container name> sleep 60 docker start <container name> sleep 30 etc etc
October 12, 20232 yr Author OK, so to be clear, the misunderstanding here is that the delays are strictly there for containers that auto start when the disk array itself is started?
September 24, 2025Sep 24 Followed this post and its recommendations, sat my containers in the right order and added the wait times; however my Emby container is ignoring that fully, it’s set to start last and with a wait from all the previous containers so that the array can initiate properly before emby starts scanning for content, because otherwise it wipes my libraries and they take a long time to re-discover.I can see the log when I initiate the array, and it shows all the containers waiting and starting in order, except for Emby; it just starts first before the array is ready.
September 24, 2025Sep 24 Community Expert 16 minutes ago, CADmin said:starts first before the array is readyAre you sure you don't have a script or something starting it? Attach Diagnostics ZIP to your NEXT post in this thread.
September 25, 2025Sep 25 10 hours ago, trurl said:Are you sure you don't have a script or something starting it?Attach Diagnostics ZIP to your NEXT post in this thread.Wouldn’t really know how to write a script to do that; i just added the container same as all others from the apps, heres the diagnostics file you requested. tower-diagnostics-20250924-0958.zip
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.