Fix some spelling typo in manual and source
infomation -> information transfered -> transferred Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
This commit is contained in:
parent
e574996911
commit
a0096535a6
|
@ -18,7 +18,7 @@ which will give the process of the container that should be joined. Namespaces f
|
||||||
be found from `/proc/[pid]/ns` and set by `setns` syscall.
|
be found from `/proc/[pid]/ns` and set by `setns` syscall.
|
||||||
|
|
||||||
And then get the pipe number from `_LIBCONTAINER_INITPIPE`, error message could
|
And then get the pipe number from `_LIBCONTAINER_INITPIPE`, error message could
|
||||||
be transfered through it. If tty is added, `_LIBCONTAINER_CONSOLE_PATH` will
|
be transferred through it. If tty is added, `_LIBCONTAINER_CONSOLE_PATH` will
|
||||||
have value and start a console for output.
|
have value and start a console for output.
|
||||||
|
|
||||||
Finally, `nsexec()` will clone a child process , exit the parent process and let
|
Finally, `nsexec()` will clone a child process , exit the parent process and let
|
||||||
|
|
|
@ -38,7 +38,7 @@ must be unique on your host.
|
||||||
An alternative for generating a customized spec config is to use "ocitools", the
|
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
|
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)
|
customizations as you want, see [ocitools](https://github.com/opencontainers/ocitools)
|
||||||
to get more infomation.
|
to get more information.
|
||||||
|
|
||||||
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
|
||||||
|
|
2
spec.go
2
spec.go
|
@ -51,7 +51,7 @@ must be unique on your host.
|
||||||
An alternative for generating a customized spec config is to use "ocitools", the
|
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
|
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)
|
customizations as you want, see [ocitools](https://github.com/opencontainers/ocitools)
|
||||||
to get more infomation.
|
to get more information.
|
||||||
|
|
||||||
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
|
||||||
|
|
Loading…
Reference in New Issue