jasder
/
runc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add infomation about ocitools in runc spec 

Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
This commit is contained in:
Qiang Huang 2016-04-21 12:57:26 +08:00
parent d14b04a331
commit 8b0d5831b8
2 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
man/runc-spec.8.md
View File

@ -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 container that you are starting. The name you provide for the container instance
must be unique on your host. 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 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 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 example: "sudo runc start container1" will give runc root privilege to start the

5
spec.go
View File

@ -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 container that you are starting. The name you provide for the container instance
must be unique on your host. 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 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 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 example: "sudo runc start container1" will give runc root privilege to start the