Customizable docker stop timeout per container rather than globally

[Alexstrasza]

A way to set the docker stop timeout (normally specified with the -t paramater in the `docker stop` command), per container rather than globally. Use case: Containers which require extra time to stop, in order to save databases and other shutdown tasks (for example, the Storj container), but without increasing system stop time in the event of a misbehaving different container. In addition, this should apply to the "stop" command in the GUI, which I'm unsure if currently obeys the system default.

 

See discussion thread: 

 

Edited May 3, 2021 by Alexstrasza

[tkohhh]

Seconded

[MrChunky]

+1

[NIronwolf]

Yep this would help a lot with save game corruption on game dockers.  Tough to tell my players the hundreds of hours of work they put in are just a garbled mess.

Edited May 3, 2021 by NIronwolf

[Alexstrasza]

3 hours ago, NIronwolf said:

Yep this would help a lot with save game corruption on game dockers.  Tough to tell my players the hundreds of hours of work they put in are just a garbled mess.

Generally speaking this isn't an issue with game containers as they can stop so quickly (within 15s or so). Do you have any specific examples?

[NIronwolf]

ARK seems to take a while.  I upped my global shutdown.  Mail server seems to want a moment to gracefully exit too.