Qiang Huang 08c7075c40 Soften limitation of update kernel memory ... Kernel memory is not allowed to be updated if container is running, it's not actually a precise kernel limitation. Before kernel version 4.6, kernel memory will not be accounted until kernel memory limit is set, if a container created with kernel memory initialized, kernel memory is accounted as soon as process created in container, so kernel memory limit update is allowed afterward. If kernel memory is not initialized, kernel memory consumed by processes in container will not be accounted, so we can't update the limit because the account will be wrong. So update kernel memory of a running container with kernel memory initialized is allowed, we should soften the limitation by docker. Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>		2016-07-12 08:07:24 +08:00
..
api	Use "on-failure" for both containers and services	2016-07-07 11:32:19 +02:00
commandline	Soften limitation of update kernel memory	2016-07-12 08:07:24 +08:00
builder.md	Fix spelling in comments, strings and documentation	2016-07-03 20:58:11 +03:00
glossary.md	Update links to Docker Hub	2016-03-04 15:48:52 +01:00
index.md	Creating Engine specific menu	2016-01-26 15:58:53 -08:00
run.md	Allow user to specify container's link-local addresses	2016-06-14 14:28:33 -07:00