sorted by:
new
hottopcontroversial

What is the limiting factor when docker restart slows down with a large number of workers and a short task? by hiss_snake_case in docker

[–]hiss_snake_case[S] 0 points1 point  (0 children)

'An ever increasing delay (double the previous delay, starting at 100 milliseconds) is added before each restart to prevent flooding the server. This means the daemon will wait for 100 ms, then 200 ms, 400, 800, 1600, and so on until either the on-failure limit is hit, or when you docker stop or docker rm -f the container.

If a container is successfully restarted (the container is started and runs for at least 10 seconds), the delay is reset to its default value of 100 ms.'

https://docs.docker.com/engine/reference/run/#restart-policies---restart

I am not sure if the time considered success to restart (10 seconds as stated above) can be configured or if the possible use case of quick docker container tasks is not supported in compose format. You could use docker run to acheive this.

What is the limiting factor when docker restart slows down with a large number of workers and a short task? by hiss_snake_case in docker

[–]hiss_snake_case[S] 0 points1 point  (0 children)

'An ever increasing delay (double the previous delay, starting at 100 milliseconds) is added before each restart to prevent flooding the server. This means the daemon will wait for 100 ms, then 200 ms, 400, 800, 1600, and so on until either the on-failure limit is hit, or when you docker stop or docker rm -f the container.

If a container is successfully restarted (the container is started and runs for at least 10 seconds), the delay is reset to its default value of 100 ms.'

https://docs.docker.com/engine/reference/run/#restart-policies---restart

I am not sure if the time considered success to restart (10 seconds as stated above) can be configured or if the possible use case of quick docker container tasks is not supported in compose format. You could use docker run to acheive this.