27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
|
# NAME
|
||
|
|
runc create - create a container
|
||
|
|
|
||
|
|
# SYNOPSIS
|
||
|
|
runc create [command options] <container-id>
|
||
|
|
|
||
|
|
Where "<container-id>" is your 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.
|
||
|
|
|
||
|
|
# DESCRIPTION
|
||
|
|
The create command creates an instance of a container for a bundle. The bundle
|
||
|
|
is a directory with a specification file named "config.json" and a root
|
||
|
|
filesystem.
|
||
|
|
|
||
|
|
The specification file includes an args parameter. The args parameter is used
|
||
|
|
to specify command(s) that get run when the container is started. To change the
|
||
|
|
command(s) that get executed on start, edit the args parameter of the spec. See
|
||
|
|
"runc spec --help" for more explanation.
|
||
|
|
|
||
|
|
# OPTIONS
|
||
|
|
--bundle value, -b value path to the root of the bundle directory, defaults to the current directory
|
||
|
|
--console value specify the pty slave path for use with the container
|
||
|
|
--pid-file value specify the file to write the process id to
|
||
|
|
--no-pivot do not use pivot root to jail process inside rootfs. This should be used whenever the rootfs is on top of a ramdisk
|
||
|
|
--no-new-keyring do not create a new session keyring for the container. This will cause the container to inherit the calling processes session key
|