From a84536eb4ace377b4bed436df5b9e06e8c1047c9 Mon Sep 17 00:00:00 2001 From: Iain MacDonald Date: Mon, 16 Jan 2023 21:03:26 +0800 Subject: [PATCH] Fix RFC3339 typo in docs Signed-off-by: Iain MacDonald --- docs/reference/commandline/container_logs.md | 2 +- docs/reference/commandline/system_prune.md | 2 +- man/src/container/logs.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/commandline/container_logs.md b/docs/reference/commandline/container_logs.md index 5fddcbdf0c..9b4d29cdd1 100644 --- a/docs/reference/commandline/container_logs.md +++ b/docs/reference/commandline/container_logs.md @@ -47,7 +47,7 @@ The `--since` option shows only the container logs generated after a given date. You can specify the date as an RFC 3339 date, a UNIX timestamp, or a Go duration string (e.g. `1m30s`, `3h`). Besides RFC3339 date format you may also use RFC3339Nano, `2006-01-02T15:04:05`, -`2006-01-02T15:04:05.999999999`, `2006-01-02Z07:00`, and `2006-01-02`. The local +`2006-01-02T15:04:05.999999999`, `2006-01-02T07:00`, and `2006-01-02`. The local timezone on the client will be used if you do not provide either a `Z` or a `+-00:00` timezone offset at the end of the timestamp. When providing Unix timestamps enter seconds[.nanoseconds], where seconds is the number of seconds diff --git a/docs/reference/commandline/system_prune.md b/docs/reference/commandline/system_prune.md index 5239821a43..04b7ace8f7 100644 --- a/docs/reference/commandline/system_prune.md +++ b/docs/reference/commandline/system_prune.md @@ -107,7 +107,7 @@ The `until` filter can be Unix timestamps, date formatted timestamps, or Go duration strings (e.g. `10m`, `1h30m`) computed relative to the daemon machine’s time. Supported formats for date formatted time stamps include RFC3339Nano, RFC3339, `2006-01-02T15:04:05`, -`2006-01-02T15:04:05.999999999`, `2006-01-02Z07:00`, and `2006-01-02`. The local +`2006-01-02T15:04:05.999999999`, `2006-01-02T07:00`, and `2006-01-02`. The local timezone on the daemon will be used if you do not provide either a `Z` or a `+-00:00` timezone offset at the end of the timestamp. When providing Unix timestamps enter seconds[.nanoseconds], where seconds is the number of seconds diff --git a/man/src/container/logs.md b/man/src/container/logs.md index 339424d148..336a73aedf 100644 --- a/man/src/container/logs.md +++ b/man/src/container/logs.md @@ -14,7 +14,7 @@ The `--since` and `--until` options can be Unix timestamps, date formatted times or Go duration strings (e.g. `10m`, `1h30m`) computed relative to the client machine's time. Supported formats for date formatted time stamps include RFC3339Nano, RFC3339, `2006-01-02T15:04:05`, `2006-01-02T15:04:05.999999999`, -`2006-01-02Z07:00`, and `2006-01-02`. The local timezone on the client will be +`2006-01-02T07:00`, and `2006-01-02`. The local timezone on the client will be used if you do not provide either a `Z` or a `+-00:00` timezone offset at the end of the timestamp. When providing Unix timestamps enter seconds[.nanoseconds], where seconds is the number of seconds that have elapsed @@ -37,4 +37,4 @@ $ docker logs -f --until=2s test Tue 14 Nov 2017 16:40:00 CET Tue 14 Nov 2017 16:40:01 CET Tue 14 Nov 2017 16:40:02 CET -``` \ No newline at end of file +```