mirror of https://github.com/docker/cli.git
Fix typos found across repository
Signed-off-by: Justas Brazauskas <brazauskasjustas@gmail.com>
This commit is contained in:
parent
53c1cb81c0
commit
b91f98d9f1
|
@ -27,11 +27,11 @@ and Docker images will report:
|
||||||
|
|
||||||
delete, import, pull, push, tag, untag
|
delete, import, pull, push, tag, untag
|
||||||
|
|
||||||
The `--since` and `--until` parameters can be Unix timestamps, date formated
|
The `--since` and `--until` parameters 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 client machine’s time. If you do not provide the --since option,
|
relative to the client machine’s time. If you do not provide the --since option,
|
||||||
the command returns only new and/or live events. Supported formats for date
|
the command returns only new and/or live events. Supported formats for date
|
||||||
formated 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-02Z07: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
|
||||||
|
|
|
@ -204,7 +204,7 @@ Respond with a string error if an error occurred.
|
||||||
{}
|
{}
|
||||||
```
|
```
|
||||||
|
|
||||||
Perform neccessary tasks to release resources help by the plugin, for example
|
Perform necessary tasks to release resources help by the plugin, for example
|
||||||
unmounting all the layered file systems.
|
unmounting all the layered file systems.
|
||||||
|
|
||||||
**Response**:
|
**Response**:
|
||||||
|
|
|
@ -43,7 +43,7 @@ values in the following formats:
|
||||||
If numeric IDs are provided, translation back to valid user or group names
|
If numeric IDs are provided, translation back to valid user or group names
|
||||||
will occur so that the subordinate uid and gid information can be read, given
|
will occur so that the subordinate uid and gid information can be read, given
|
||||||
these resources are name-based, not id-based. If the numeric ID information
|
these resources are name-based, not id-based. If the numeric ID information
|
||||||
provided does not exist as entries in `/etc/passwd` or `/etc/group`, dameon
|
provided does not exist as entries in `/etc/passwd` or `/etc/group`, daemon
|
||||||
startup will fail with an error message.
|
startup will fail with an error message.
|
||||||
|
|
||||||
*An example: starting with default Docker user management:*
|
*An example: starting with default Docker user management:*
|
||||||
|
@ -67,7 +67,7 @@ create the following range, based on an existing user already having the first
|
||||||
|
|
||||||
> **Note:** On a fresh Fedora install, we found that we had to `touch` the
|
> **Note:** On a fresh Fedora install, we found that we had to `touch` the
|
||||||
> `/etc/subuid` and `/etc/subgid` files to have ranges assigned when users
|
> `/etc/subuid` and `/etc/subgid` files to have ranges assigned when users
|
||||||
> were created. Once these files existed, range assigment on user creation
|
> were created. Once these files existed, range assignment on user creation
|
||||||
> worked properly.
|
> worked properly.
|
||||||
|
|
||||||
If you have a preferred/self-managed user with subordinate ID mappings already
|
If you have a preferred/self-managed user with subordinate ID mappings already
|
||||||
|
|
|
@ -37,11 +37,11 @@ and Docker images will report:
|
||||||
**--until**=""
|
**--until**=""
|
||||||
Stream events until this timestamp
|
Stream events until this timestamp
|
||||||
|
|
||||||
The `--since` and `--until` parameters can be Unix timestamps, date formated
|
The `--since` and `--until` parameters 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 client machine’s time. If you do not provide the --since option,
|
relative to the client machine’s time. If you do not provide the --since option,
|
||||||
the command returns only new and/or live events. Supported formats for date
|
the command returns only new and/or live events. Supported formats for date
|
||||||
formated 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-02Z07: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
|
||||||
|
|
|
@ -48,7 +48,7 @@ the running containers.
|
||||||
.Ports - Exposed ports.
|
.Ports - Exposed ports.
|
||||||
.Status - Container status.
|
.Status - Container status.
|
||||||
.Size - Container disk size.
|
.Size - Container disk size.
|
||||||
.Labels - All labels asigned to the container.
|
.Labels - All labels assigned to the container.
|
||||||
.Label - Value of a specific label for this container. For example `{{.Label "com.docker.swarm.cpu"}}`
|
.Label - Value of a specific label for this container. For example `{{.Label "com.docker.swarm.cpu"}}`
|
||||||
|
|
||||||
**--help**
|
**--help**
|
||||||
|
|
Loading…
Reference in New Issue