Fix RFC3339 typo in docs

Signed-off-by: Iain MacDonald <ijmacd@gmail.com>
This commit is contained in:
Iain MacDonald 2023-01-16 21:03:26 +08:00 committed by Paweł Gronowski
parent 158348412d
commit a84536eb4a
3 changed files with 4 additions and 4 deletions

View File

@ -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 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 timestamp, or a Go duration string (e.g. `1m30s`, `3h`). Besides RFC3339 date
format you may also use RFC3339Nano, `2006-01-02T15:04:05`, 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 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 `+-00:00` timezone offset at the end of the timestamp. When providing Unix
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds timestamps enter seconds[.nanoseconds], where seconds is the number of seconds

View File

@ -107,7 +107,7 @@ The `until` filter can be Unix timestamps, date formatted
timestamps, or Go duration strings (e.g. `10m`, `1h30m`) computed timestamps, or Go duration strings (e.g. `10m`, `1h30m`) computed
relative to the daemon machines time. Supported formats for date relative to the daemon machines time. Supported formats for date
formatted time stamps include RFC3339Nano, RFC3339, `2006-01-02T15:04:05`, 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 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 `+-00:00` timezone offset at the end of the timestamp. When providing Unix
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds timestamps enter seconds[.nanoseconds], where seconds is the number of seconds

View File

@ -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 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, time. Supported formats for date formatted time stamps include RFC3339Nano,
RFC3339, `2006-01-02T15:04:05`, `2006-01-02T15:04:05.999999999`, 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 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 end of the timestamp. When providing Unix timestamps enter
seconds[.nanoseconds], where seconds is the number of seconds that have elapsed 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:00 CET
Tue 14 Nov 2017 16:40:01 CET Tue 14 Nov 2017 16:40:01 CET
Tue 14 Nov 2017 16:40:02 CET Tue 14 Nov 2017 16:40:02 CET
``` ```