From 6ef65b74e14360637d925302ca5f518e5a411988 Mon Sep 17 00:00:00 2001 From: Alban Crequy Date: Wed, 27 Jun 2018 14:36:29 +0200 Subject: [PATCH] Document how to use systemd-run It is also useful when testing local changes, I just run: sudo systemd-run -p Delegate=yes -p KillMode=process bin/containerd Signed-off-by: Alban Crequy --- docs/ops.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/ops.md b/docs/ops.md index 2ac67b1de..1d842eb68 100644 --- a/docs/ops.md +++ b/docs/ops.md @@ -69,6 +69,10 @@ This is not what we want. As ops, we want to be able to upgrade containerd and allow existing containers to keep running without interruption. Setting `KillMode` to `process` ensures that systemd only kills the containerd daemon and not any child processes such as the shims and containers. +The following `systemd-run` command starts containerd in a similar way: +``` +sudo systemd-run -p Delegate=yes -p KillMode=process /usr/local/bin/containerd +``` ## Base Configuration