From 4cfbd2555d280a107c207bd02bf86928f8dab950 Mon Sep 17 00:00:00 2001 From: rajasec Date: Sat, 22 Oct 2016 22:52:18 +0530 Subject: [PATCH] Small typo in README Signed-off-by: rajasec Fixing small typo in README Signed-off-by: rajasec --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4bca381a..df42c0a5 100644 --- a/README.md +++ b/README.md @@ -107,7 +107,7 @@ runc run mycontainerid If you used the unmodified `runc spec` template this should give you a `sh` session inside the container. The second way to start a container is using the specs lifecycle operations. -This gives you move power of how the container is created and managed while it is running. +This gives you more power over how the container is created and managed while it is running. This will also launch the container in the background so you will have to edit the `config.json` to remove the `terminal` setting for the simple examples here. Your process field in the `config.json` should look like this below with `"terminal": false` and `"args": ["sleep", "5"]`.