Docker start order and delays not working

[Merijeek]

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?

 

 

 

[JonathanM]

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.

[Merijeek]

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? 

[JonathanM]

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

[Merijeek]

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? 

[JonathanM]

When the docker service starts, yes.