mirror of https://github.com/docker/docs.git
engine: refresh cli reference (24.0)
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
parent
6dd9522756
commit
45a61b38bf
|
@ -38,30 +38,6 @@ long: |-
|
||||||
performance critical applications that generate a lot of output in the
|
performance critical applications that generate a lot of output in the
|
||||||
foreground over a slow client connection. Instead, users should use the
|
foreground over a slow client connection. Instead, users should use the
|
||||||
`docker logs` command to get access to the logs.
|
`docker logs` command to get access to the logs.
|
||||||
|
|
||||||
### Override the detach sequence
|
|
||||||
|
|
||||||
If you want, you can configure an override the Docker key sequence for detach.
|
|
||||||
This is useful if the Docker default sequence conflicts with key sequence you
|
|
||||||
use for other applications. There are two ways to define your own detach key
|
|
||||||
sequence, as a per-container override or as a configuration property on your
|
|
||||||
entire configuration.
|
|
||||||
|
|
||||||
To override the sequence for an individual container, use the
|
|
||||||
`--detach-keys="<sequence>"` flag with the `docker attach` command. The format of
|
|
||||||
the `<sequence>` is either a letter [a-Z], or the `ctrl-` combined with any of
|
|
||||||
the following:
|
|
||||||
|
|
||||||
* `a-z` (a single lowercase alpha character )
|
|
||||||
* `@` (at sign)
|
|
||||||
* `[` (left bracket)
|
|
||||||
* `\\` (two backward slashes)
|
|
||||||
* `_` (underscore)
|
|
||||||
* `^` (caret)
|
|
||||||
|
|
||||||
These `a`, `ctrl-a`, `X`, or `ctrl-\\` values are all examples of valid key
|
|
||||||
sequences. To configure a different configuration default key sequence for all
|
|
||||||
containers, see [**Configuration file** section](cli.md#configuration-files).
|
|
||||||
usage: docker attach [OPTIONS] CONTAINER
|
usage: docker attach [OPTIONS] CONTAINER
|
||||||
pname: docker
|
pname: docker
|
||||||
plink: docker.yaml
|
plink: docker.yaml
|
||||||
|
@ -69,6 +45,7 @@ options:
|
||||||
- option: detach-keys
|
- option: detach-keys
|
||||||
value_type: string
|
value_type: string
|
||||||
description: Override the key sequence for detaching a container
|
description: Override the key sequence for detaching a container
|
||||||
|
details_url: '#detach-keys'
|
||||||
deprecated: false
|
deprecated: false
|
||||||
hidden: false
|
hidden: false
|
||||||
experimental: false
|
experimental: false
|
||||||
|
@ -193,6 +170,30 @@ examples: |-
|
||||||
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
||||||
a2fe3fd886db alpine "/bin/sh" About a minute ago Exited (13) 40 seconds ago test
|
a2fe3fd886db alpine "/bin/sh" About a minute ago Exited (13) 40 seconds ago test
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Override the detach sequence (--detach-keys) {#detach-keys}
|
||||||
|
|
||||||
|
Use the `--detach-keys` option to override the Docker key sequence for detach.
|
||||||
|
This is useful if the Docker default sequence conflicts with key sequence you
|
||||||
|
use for other applications. There are two ways to define your own detach key
|
||||||
|
sequence, as a per-container override or as a configuration property on your
|
||||||
|
entire configuration.
|
||||||
|
|
||||||
|
To override the sequence for an individual container, use the
|
||||||
|
`--detach-keys="<sequence>"` flag with the `docker attach` command. The format of
|
||||||
|
the `<sequence>` is either a letter [a-Z], or the `ctrl-` combined with any of
|
||||||
|
the following:
|
||||||
|
|
||||||
|
* `a-z` (a single lowercase alpha character )
|
||||||
|
* `@` (at sign)
|
||||||
|
* `[` (left bracket)
|
||||||
|
* `\\` (two backward slashes)
|
||||||
|
* `_` (underscore)
|
||||||
|
* `^` (caret)
|
||||||
|
|
||||||
|
These `a`, `ctrl-a`, `X`, or `ctrl-\\` values are all examples of valid key
|
||||||
|
sequences. To configure a different configuration default key sequence for all
|
||||||
|
containers, see [**Configuration file** section](cli.md#configuration-files).
|
||||||
deprecated: false
|
deprecated: false
|
||||||
experimental: false
|
experimental: false
|
||||||
experimentalcli: false
|
experimentalcli: false
|
||||||
|
|
|
@ -233,6 +233,7 @@ options:
|
||||||
- option: detach-keys
|
- option: detach-keys
|
||||||
value_type: string
|
value_type: string
|
||||||
description: Override the key sequence for detaching a container
|
description: Override the key sequence for detaching a container
|
||||||
|
details_url: '#detach-keys'
|
||||||
deprecated: false
|
deprecated: false
|
||||||
hidden: false
|
hidden: false
|
||||||
experimental: false
|
experimental: false
|
||||||
|
@ -1428,10 +1429,12 @@ examples: |-
|
||||||
```
|
```
|
||||||
|
|
||||||
You can also choose the IP addresses for the container with `--ip` and `--ip6`
|
You can also choose the IP addresses for the container with `--ip` and `--ip6`
|
||||||
flags when you start the container on a user-defined network.
|
flags when you start the container on a user-defined network. To assign a
|
||||||
|
static IP to containers, you must specify subnet block for the network.
|
||||||
|
|
||||||
```console
|
```console
|
||||||
$ docker run -itd --network=my-net --ip=10.10.9.75 busybox
|
$ docker network create --subnet 192.0.2.0/24 my-net
|
||||||
|
$ docker run -itd --network=my-net --ip=192.0.2.69 busybox
|
||||||
```
|
```
|
||||||
|
|
||||||
If you want to add a running container to a network use the `docker network connect` subcommand.
|
If you want to add a running container to a network use the `docker network connect` subcommand.
|
||||||
|
@ -1512,6 +1515,30 @@ examples: |-
|
||||||
|
|
||||||
See also [the `docker cp` command](cp.md).
|
See also [the `docker cp` command](cp.md).
|
||||||
|
|
||||||
|
### Override the detach sequence (--detach-keys) {#detach-keys}
|
||||||
|
|
||||||
|
Use the `--detach-keys` option to override the Docker key sequence for detach.
|
||||||
|
This is useful if the Docker default sequence conflicts with key sequence you
|
||||||
|
use for other applications. There are two ways to define your own detach key
|
||||||
|
sequence, as a per-container override or as a configuration property on your
|
||||||
|
entire configuration.
|
||||||
|
|
||||||
|
To override the sequence for an individual container, use the
|
||||||
|
`--detach-keys="<sequence>"` flag with the `docker attach` command. The format of
|
||||||
|
the `<sequence>` is either a letter [a-Z], or the `ctrl-` combined with any of
|
||||||
|
the following:
|
||||||
|
|
||||||
|
* `a-z` (a single lowercase alpha character )
|
||||||
|
* `@` (at sign)
|
||||||
|
* `[` (left bracket)
|
||||||
|
* `\\` (two backward slashes)
|
||||||
|
* `_` (underscore)
|
||||||
|
* `^` (caret)
|
||||||
|
|
||||||
|
These `a`, `ctrl-a`, `X`, or `ctrl-\\` values are all examples of valid key
|
||||||
|
sequences. To configure a different configuration default key sequence for all
|
||||||
|
containers, see [**Configuration file** section](cli.md#configuration-files).
|
||||||
|
|
||||||
### Add host device to container (--device) {#device}
|
### Add host device to container (--device) {#device}
|
||||||
|
|
||||||
```console
|
```console
|
||||||
|
|
Loading…
Reference in New Issue