mirror/runc
1
0
Fork 0
mirror of https://github.com/opencontainers/runc.git synced 2026-07-11 06:03:57 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #765 from hqhq/hq_link_ocitools

Browse Source 
Add infomation about ocitools in runc spec
This commit is contained in:
Mrunal Patel
2016-04-21 09:53:30 -07:00
parent d14b04a331 8b0d5831b8
commit 1d2bea3d46
2 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/runc-spec.8.md
+5
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
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
spec.go
+5
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
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