mirror of https://github.com/docker/cli.git
docs: typo fixes and other corrections
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
parent
d17b3b2d80
commit
4bb2abaa54
|
@ -69,7 +69,7 @@ user credentials, VPNs, and so forth.
|
|||
> **Note**
|
||||
>
|
||||
> If the `URL` parameter contains a fragment the system recursively clones
|
||||
> the repository and its submodules using a `git clone --recursive` command.
|
||||
> the repository and its submodules.
|
||||
|
||||
Git URLs accept context configuration in their fragment section, separated by a
|
||||
colon (`:`). The first part represents the reference that Git checks out,
|
||||
|
|
|
@ -1347,7 +1347,7 @@ using the `daemon.json` file.
|
|||
"default-network-opts": {
|
||||
"bridge": {
|
||||
"com.docker.network.bridge.host_binding_ipv4": "127.0.0.1",
|
||||
"com.docker.network.bridge.mtu": "1234"
|
||||
"com.docker.network.driver.mtu": "1234"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
@ -1363,7 +1363,7 @@ you create use these option configurations as defaults.
|
|||
```console
|
||||
$ docker network create mynet
|
||||
$ docker network inspect mynet --format "{{json .Options}}"
|
||||
{"com.docker.network.bridge.host_binding_ipv4":"127.0.0.1","com.docker.network.bridge.mtu":"1234"}
|
||||
{"com.docker.network.bridge.host_binding_ipv4":"127.0.0.1","com.docker.network.driver.mtu":"1234"}
|
||||
```
|
||||
|
||||
Note that changing this daemon configuration doesn't affect pre-existing
|
||||
|
@ -1377,5 +1377,5 @@ daemon configuration. The CLI flag expects a value with the following format:
|
|||
```console
|
||||
$ sudo dockerd \
|
||||
--default-network-opt bridge=com.docker.network.bridge.host_binding_ipv4=127.0.0.1 \
|
||||
--default-network-opt bridge=com.docker.network.bridge.mtu=1234
|
||||
--default-network-opt bridge=com.docker.network.driver.mtu=1234
|
||||
```
|
||||
|
|
|
@ -7,7 +7,7 @@ title: Running containers
|
|||
---
|
||||
|
||||
Docker runs processes in isolated containers. A container is a process
|
||||
which runs on a host. The host may be local or remote. When an you
|
||||
which runs on a host. The host may be local or remote. When you
|
||||
execute `docker run`, the container process that runs is isolated in
|
||||
that it has its own file system, its own networking, and its own
|
||||
isolated process tree separate from the host.
|
||||
|
|
Loading…
Reference in New Issue