github/containerd
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

This config no longer exists, so remove from docs.

Browse Source 
This was changed to `no_subreaper` in
6e9f24b711 and, as far as I can tell,
`no_subreaper` doesn't exist as a config anymore.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
This commit is contained in:
Brian Goff 2020-04-17 14:12:44 -07:00
parent d8506bfd7b
commit 8574083153
2 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/getting-started.md
View File

@ -19,7 +19,6 @@ The daemon also uses a configuration file located in `/etc/containerd/config.tom
A sample configuration file looks like this: A sample configuration file looks like this:
```toml ```toml
subreaper = true
oom_score = -999 oom_score = -999
[debug] [debug]

5
docs/ops.md
View File

@ -82,9 +82,6 @@ There are a few settings that are important for ops.
The first setting is the `oom_score`. Because containerd will be managing multiple containers, we need to ensure that containers are killed before the containerd daemon in an out of memory condition. The first setting is the `oom_score`. Because containerd will be managing multiple containers, we need to ensure that containers are killed before the containerd daemon in an out of memory condition.
We also do not want to make containerd unkillable, but we want to lower its score to the level of other system daemons. We also do not want to make containerd unkillable, but we want to lower its score to the level of other system daemons.
The `subreaper` setting is also important on linux systems.
This allows containerd to reap any re-parented processes from the shims or containers.
containerd also exports its own metrics as well as container level metrics via the prometheus metrics format. containerd also exports its own metrics as well as container level metrics via the prometheus metrics format.
Currently, prometheus only supports TCP endpoints, therefore, the metrics address should be a TCP address that your prometheus infrastructure can scrape metrics from. Currently, prometheus only supports TCP endpoints, therefore, the metrics address should be a TCP address that your prometheus infrastructure can scrape metrics from.
@ -161,8 +158,6 @@ External apps reading or watching changes in these directories have been known t
root = "/var/lib/containerd" root = "/var/lib/containerd"
# runtime state information # runtime state information
state = "/run/containerd" state = "/run/containerd"
# set containerd as a subreaper on linux when it is not running as PID 1
subreaper = true
# set containerd's OOM score # set containerd's OOM score
oom_score = -999 oom_score = -999