mirror of https://github.com/docker/cli.git
docs: move --cgroup-parent to docker run reference
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
parent
9e75a4cf61
commit
72df1960e1
|
@ -18,7 +18,7 @@ Create and run a new container from an image
|
||||||
| `--blkio-weight-device` | `list` | | Block IO weight (relative device weight) |
|
| `--blkio-weight-device` | `list` | | Block IO weight (relative device weight) |
|
||||||
| `--cap-add` | `list` | | Add Linux capabilities |
|
| `--cap-add` | `list` | | Add Linux capabilities |
|
||||||
| `--cap-drop` | `list` | | Drop Linux capabilities |
|
| `--cap-drop` | `list` | | Drop Linux capabilities |
|
||||||
| `--cgroup-parent` | `string` | | Optional parent cgroup for the container |
|
| [`--cgroup-parent`](#cgroup-parent) | `string` | | Optional parent cgroup for the container |
|
||||||
| `--cgroupns` | `string` | | Cgroup namespace to use (host\|private)<br>'host': Run the container in the Docker host's cgroup namespace<br>'private': Run the container in its own private cgroup namespace<br>'': Use the cgroup namespace as configured by the<br> default-cgroupns-mode option on the daemon (default) |
|
| `--cgroupns` | `string` | | Cgroup namespace to use (host\|private)<br>'host': Run the container in the Docker host's cgroup namespace<br>'private': Run the container in its own private cgroup namespace<br>'': Use the cgroup namespace as configured by the<br> default-cgroupns-mode option on the daemon (default) |
|
||||||
| [`--cidfile`](#cidfile) | `string` | | Write the container ID to the file |
|
| [`--cidfile`](#cidfile) | `string` | | Write the container ID to the file |
|
||||||
| `--cpu-count` | `int64` | `0` | CPU count (Windows only) |
|
| `--cpu-count` | `int64` | `0` | CPU count (Windows only) |
|
||||||
|
@ -949,6 +949,13 @@ You can use the `-t` flag without `-i` flag. This still allocates a pseudo-TTY
|
||||||
to the container, but with no way of writing to `STDIN`. The only time this
|
to the container, but with no way of writing to `STDIN`. The only time this
|
||||||
might be useful is if the output of the container requires a TTY environment.
|
might be useful is if the output of the container requires a TTY environment.
|
||||||
|
|
||||||
|
## <a name="cgroup-parent"></a> Specify custom cgroups
|
||||||
|
|
||||||
|
Using the `--cgroup-parent` flag, you can pass a specific cgroup to run a
|
||||||
|
container in. This allows you to create and manage cgroups on their own. You can
|
||||||
|
define custom resources for those cgroups and put containers under a common
|
||||||
|
parent group.
|
||||||
|
|
||||||
### <a name="device-cgroup-rule"></a> Using dynamically created devices (--device-cgroup-rule)
|
### <a name="device-cgroup-rule"></a> Using dynamically created devices (--device-cgroup-rule)
|
||||||
|
|
||||||
Docker assigns devices available to a container at creation time. The
|
Docker assigns devices available to a container at creation time. The
|
||||||
|
|
|
@ -241,13 +241,6 @@ $ echo $?
|
||||||
3
|
3
|
||||||
```
|
```
|
||||||
|
|
||||||
## Specify custom cgroups
|
|
||||||
|
|
||||||
Using the `--cgroup-parent` flag, you can pass a specific cgroup to run a
|
|
||||||
container in. This allows you to create and manage cgroups on their own. You can
|
|
||||||
define custom resources for those cgroups and put containers under a common
|
|
||||||
parent group.
|
|
||||||
|
|
||||||
## Runtime constraints on resources
|
## Runtime constraints on resources
|
||||||
|
|
||||||
The operator can also adjust the performance parameters of the
|
The operator can also adjust the performance parameters of the
|
||||||
|
|
Loading…
Reference in New Issue