Instructions for using "wait"

[autumnwalker]

Hello, I used to use the Docker Autostart Manager to start certain containers after a period of time and that plugin has been depreciated in 6.6. I understand that I can now switch to the advanced view and add a "wait" metric to each container, but I cannot find documentation on how it works.

 

1. Is the "wait" metric seconds, minutes?
2. Does "wait" instruct the docker with the "wait" to wait, or does it instruct Unraid to wait X before starting the next container?

 

I've figured out that containers start sequentially and can be re-ordered by click + drag.

 

Thanks!

[Squid]

Its in seconds, and its the time to wait after starting

[TRaSH]

i got the feeling it kinda ignores the settings,

or i'm doing something wrong.

 

 

why would Emby start earlier then krusader or nzbget ?

[Squid]

1 hour ago, TRaSH said:

why would Emby start earlier then krusader or nzbget ?

Because its first in the list.  Drag the rows to rearrange the order

[JonathanM]

1 hour ago, TRaSH said:

why would Emby start earlier then krusader or nzbget ?

Because it's first in the list?

Based on your screenshot, you told unraid to

Start Emby, then wait 100+ seconds

Start Krusader, then wait 30 seconds

Etc.

[TRaSH]

thnx,
didn't know you could arrange them like this.
thnx for the help

[SiRMarlon]

This just answered the question I had! Good ol search function!  

[snake_t]

Wow! This Docker page really lacks instructions! but thanks to you guys, I finally figure out how to use this wait functionality!

[ados]

I cannot seem to get this to work for me.
Based on what has been said, it does not wait to start the docker but instead starts it and then asks to wait.

If that's the case it would explain why its not working for me, I'm intending to control the internal IP order as I need dockers to communicate directly and thus need the IP to remain the same. I am aware of the custom IP but cannot use that, am I up a creek without a paddle?

[NewDisplayName]

i dont understand your problem.

 

but i just added a "custom network" to my docker who need to connect together and then i just use their name as ip so instead of 1.1.1.1:2000 i use nzbget:2000 and yes that even works in configs

Edited September 8, 2021 by nuhll

[EDalcin]

On 6/22/2019 at 10:13 AM, Squid said:

Because its first in the list.  Drag the rows to rearrange the order

I can't "drag". Where should I click? Should I enable first the "drag" funcion?

[JonathanM]

On 12/8/2023 at 1:57 AM, EDalcin said:

I can't "drag". Where should I click? Should I enable first the "drag" funcion?

Is the page unlocked at the top right?

[knights_of_pine]

is this the same way to delay a docker from starting up after the plugin AppData backup runs?  i have a docker of JellyStats and it really does not like starting until Jellyfin is started and running for at least like 2 minutes.  Right now Jellystat just tries to stop then dies and have to manually start it.

 

thank you for the help!

[groot-stuff]

On 1/24/2024 at 9:24 PM, knights_of_pine said:

is this the same way to delay a docker from starting up after the plugin AppData backup runs?  i have a docker of JellyStats and it really does not like starting until Jellyfin is started and running for at least like 2 minutes.  Right now Jellystat just tries to stop then dies and have to manually start it.

 

thank you for the help!

 

Correct, the Wait/Delay set in the Docker tab is utilized by the Backup/Restore Appdata plugin as well.  You can verify this in the logs (see below).

 

Also - groups can be defined in the Backup/Restore Appdata plugin to ensure container dependencies are cared for (discovered this recently).

 

Which can be set by clicking on the docker container when on the settings tab of the Backup/Restore Appdata plugin.

Just set the Member of group to the same value for all related docker containers and save (then they will show up like my immich ones above).

 

 

Edited July 24 by groot-stuff