mirror of https://github.com/docker/cli.git
Fix spelling in comments, strings and documentation
Signed-off-by: Otto Kekäläinen <otto@seravo.fi>
This commit is contained in:
parent
0f61955bdb
commit
8e2c3efc58
|
@ -502,7 +502,7 @@ default is `/bin/sh -c` on Linux or `cmd /S /C` on Windows)
|
|||
- `RUN ["executable", "param1", "param2"]` (*exec* form)
|
||||
|
||||
The `RUN` instruction will execute any commands in a new layer on top of the
|
||||
current image and commit the results. The resulting committed image will be
|
||||
current image and commit the results. The resulting comitted image will be
|
||||
used for the next step in the `Dockerfile`.
|
||||
|
||||
Layering `RUN` instructions and generating commits conforms to the core
|
||||
|
@ -544,7 +544,7 @@ RUN /bin/bash -c 'source $HOME/.bashrc ; echo $HOME'
|
|||
>
|
||||
> **Note**:
|
||||
> In the *JSON* form, it is necessary to escape backslashes. This is
|
||||
> particularly relevant on Windows where the backslash is the path seperator.
|
||||
> particularly relevant on Windows where the backslash is the path separator.
|
||||
> The following line would otherwise be treated as *shell* form due to not
|
||||
> being valid JSON, and fail in an unexpected way:
|
||||
> `RUN ["c:\windows\system32\tasklist.exe"]`
|
||||
|
|
|
@ -49,7 +49,7 @@ This example displays images with a name containing 'busybox':
|
|||
ofayau/busybox-libc32 Busybox with 32 bits (and 64 bits) libs 1 [OK]
|
||||
peelsky/zulu-openjdk-busybox 1 [OK]
|
||||
skomma/busybox-data Docker image suitable for data volume cont... 1 [OK]
|
||||
elektritter/busybox-teamspeak Leightweight teamspeak3 container based on... 1 [OK]
|
||||
elektritter/busybox-teamspeak Lightweight teamspeak3 container based on... 1 [OK]
|
||||
socketplane/busybox 1 [OK]
|
||||
oveits/docker-nginx-busybox This is a tiny NginX docker image based on... 0 [OK]
|
||||
ggtools/busybox-ubuntu Busybox ubuntu version with extra goodies 0 [OK]
|
||||
|
|
|
@ -38,7 +38,7 @@ ID NAME MEMBERSHIP STATUS AVAILABILITY MANAGER
|
|||
### `--auto-accept value`
|
||||
|
||||
This flag controls node acceptance into the cluster. By default, `worker` nodes are
|
||||
automatically accepted by the cluster. This can be changed by specifing what kinds of nodes
|
||||
automatically accepted by the cluster. This can be changed by specifying what kinds of nodes
|
||||
can be auto-accepted into the cluster. If auto-accept is not turned on, then
|
||||
[node accept](node_accept.md) can be used to explicitly accept a node into the cluster.
|
||||
|
||||
|
|
|
@ -627,7 +627,7 @@ docker network create -d ipvlan \
|
|||
|
||||
|
||||
# Start a few of containers on the network (ipnet110)
|
||||
# in seperate terminals and check connectivity
|
||||
# in separate terminals and check connectivity
|
||||
docker run --net=ipnet110 -it --rm alpine /bin/sh
|
||||
# Start a second container specifying the v6 address
|
||||
docker run --net=ipnet110 --ip6=2001:db8:abc6::10 -it --rm alpine /bin/sh
|
||||
|
|
Loading…
Reference in New Issue