Skip to content
This repository was archived by the owner on Jul 18, 2025. It is now read-only.

Conversation

@yongtang
Copy link
Contributor

This fix tries to add config paramter to change per-contaienr stop timeout during the daemon shutdown. As the part of the update, this fix also changes docker restart and docker stop so that if --time is not specified, then the default stop timeout (10s) will be used.

This fix is related to
moby/moby#22566
moby/moby#22471

Signed-off-by: Yong Tang yong.tang.github@outlook.com

…on shutdown

This fix tries to add config paramter to change per-contaienr stop timeout during
the daemon shutdown. As the part of the update, this fix also changes `docker restart`
and `docker stop` so that if `--time` is not specified, then the default stop timeout
(10s) will be used.

This fix is related to
moby/moby#22566
moby/moby#22471

Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
@thaJeztah
Copy link
Contributor

LGTM

1 similar comment
@calavera
Copy link
Contributor

LGTM

@calavera calavera merged commit f50fbe5 into docker-archive-public:master Jun 15, 2016
@yongtang yongtang deleted the 22471-daemon-shutdown-timeout branch July 15, 2016 22:41
@stevvooe
Copy link
Contributor

stevvooe commented Sep 8, 2016

"Make the zero-value useful"

Could we please stop adding needless pointer values everywhere? This is getting tiresome. 1ns is just as good as zero and doesn't cause all kinds of havoc.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants