From 93a4d96e98a5ea0476a003868de13e023692cc27 Mon Sep 17 00:00:00 2001 From: Yong Tang Date: Sun, 8 May 2016 16:11:34 -0700 Subject: [PATCH] Emit events for docker daemon This fix tries to cover the issue raised in #22463 by emitting events for docker daemon so that user could be notified by scenarios like config reload, etc. This fix adds the `daemon reload`, and events for docker daemon. Additional tests have been added to cover the changes in this fix. This fix fixes #22463. Signed-off-by: Yong Tang Upstream-commit: 91466baa3f127b3b6d8ffbb0ca80c9559adc1559 Component: cli --- components/cli/docs/reference/commandline/events.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/components/cli/docs/reference/commandline/events.md b/components/cli/docs/reference/commandline/events.md index 0abfdf4377..5a7b85f3cb 100644 --- a/components/cli/docs/reference/commandline/events.md +++ b/components/cli/docs/reference/commandline/events.md @@ -35,6 +35,10 @@ Docker networks report the following events: create, connect, disconnect, destroy +Docker daemon report the following events: + + reload + The `--since` and `--until` parameters can be Unix timestamps, date formatted timestamps, or Go duration strings (e.g. `10m`, `1h30m`) computed relative to the client machine’s time. If you do not provide the `--since` option,