From 8b0d5831b8064d6ad1bcb4706a1a2d4271860851 Mon Sep 17 00:00:00 2001 From: Qiang Huang Date: Thu, 21 Apr 2016 12:57:26 +0800 Subject: [PATCH] Add infomation about ocitools in runc spec Signed-off-by: Qiang Huang --- man/runc-spec.8.md | 5 +++++ spec.go | 5 +++++ 2 files changed, 10 insertions(+) diff --git a/man/runc-spec.8.md b/man/runc-spec.8.md index 71db7c98..b2b2915d 100644 --- a/man/runc-spec.8.md +++ b/man/runc-spec.8.md @@ -35,6 +35,11 @@ In the start command above, "container1" is the name for the instance of the container that you are starting. The name you provide for the container instance must be unique on your host. +An alternative for generating a customized spec config is to use "ocitools", the +sub-command "ocitools generate" has lots of options that can be used to do any +customizations as you want, see [ocitools](https://github.com/opencontainers/ocitools) +to get more infomation. + When starting a container through runc, runc needs root privilege. If not already running as root, you can use sudo to give runc root privilege. For example: "sudo runc start container1" will give runc root privilege to start the diff --git a/spec.go b/spec.go index 69ea1e50..0ecf75f0 100644 --- a/spec.go +++ b/spec.go @@ -48,6 +48,11 @@ In the start command above, "container1" is the name for the instance of the container that you are starting. The name you provide for the container instance must be unique on your host. +An alternative for generating a customized spec config is to use "ocitools", the +sub-command "ocitools generate" has lots of options that can be used to do any +customizations as you want, see [ocitools](https://github.com/opencontainers/ocitools) +to get more infomation. + When starting a container through runc, runc needs root privilege. If not already running as root, you can use sudo to give runc root privilege. For example: "sudo runc start container1" will give runc root privilege to start the