% crio(8) Open Container Initiative Daemon % Dan Walsh % SEPTEMBER 2016
crio - OCI Kubernetes Container Runtime daemon
crio [--apparmor-profile=[value]] [--cgroup-manager=[value]] [--cni-config-dir=[value]] [--cni-plugin-dir=[value]] [--config=[value]] [--conmon=[value]] [--cpu-profile=[value]] [--debug] [--default-transport=[value]] [--help|-h] [--insecure-registry=[value]] [--listen=[value]] [--log=[value]] [--log-format value] [--pause-command=[value]] [--pause-image=[value]] [--registry=[value]] [--root=[value]] [--runroot=[value]] [--runtime=[value]] [--seccomp-profile=[value]] [--selinux] [--signature-policy=[value]] [--storage-driver=[value]] [--storage-opt=[value]] [--version|-v]
OCI-based implementation of Kubernetes Container Runtime Interface Daemon
crio is meant to provide an integration path between OCI conformant runtimes and the kubelet. Specifically, it implements the Kubelet Container Runtime Interface (CRI) using OCI conformant runtimes. The scope of crio is tied to the scope of the CRI.
* Support multiple image formats including the existing Docker image format
* Support for multiple means to download images including trust & image verification
* Container image management (managing image layers, overlay filesystems, etc)
* Container process lifecycle management
* Monitoring and logging required to satisfy the CRI
* Resource isolation as required by the CRIcrio [GLOBAL OPTIONS]
crio [GLOBAL OPTIONS] config [OPTIONS]
--apparmor_profile="" Name of the apparmor profile to be used as the runtime's default (default: "crio-default")
--cgroup-manager="" cgroup manager (cgroupfs or systemd)
--config="" path to configuration file
--conmon="" path to the conmon executable (default: "/usr/local/libexec/crio/conmon")
--cpu-profile="" set the CPU profile file path
--debug Enable debug output for logging
--default-transport A prefix to prepend to image names that can't be pulled as-is.
--help, -h Print usage statement
--insecure-registry= Enable insecure registry communication, i.e., enable un-encrypted and/or untrusted communication.
List of insecure registries can contain an element with CIDR notation to specify a whole subnet. Insecure registries accept HTTP and/or accept HTTPS with certificates from unknown CAs.
Enabling --insecure-registry is useful when running a local registry. However, because its use creates security vulnerabilities it should ONLY be enabled for testing purposes. For increased security, users should add their CA to their system's list of trusted CAs instead of using --insecure-registry.
--image-volumes="" Image volume handling ('mkdir' or 'ignore') (default: "mkdir")
--listen="" Path to crio socket (default: "/var/run/crio.sock")
--log="" Set the log file path where internal debug information is written
--log-format="" Set the format used by logs ('text' (default), or 'json') (default: "text")
--pause-command="" Path to the pause executable in the pause image (default: "/pause")
--pause-image="" Image which contains the pause executable (default: "kubernetes/pause")
--pids-limit="" Maximum number of processes allowed in a container (default: 1024)
--root="" CRIO root dir (default: "/var/lib/containers/storage")
--registry="" Registry host which will be prepended to unqualified images, can be specified multiple times
--runroot="" CRIO state dir (default: "/var/run/containers/storage")
--runtime="" OCI runtime path (default: "/usr/bin/runc")
--selinux=true|false Enable selinux support (default: false)
--seccomp-profile="" Path to the seccomp json profile to be used as the runtime's default (default: "/etc/crio/seccomp.json")
--signature-policy="" Path to the signature policy json file (default: "", to use the system-wide default)
--storage-driver OCI storage driver (default: "devicemapper")
--storage-opt OCI storage driver option (no default)
--cni-config-dir="" CNI configuration files directory (default: "/etc/cni/net.d/")
--cni-plugin-dir="" CNI plugin binaries directory (default: "/opt/cni/bin/")
--cpu-profile Set the CPU profile file path
--version, -v Print the version
CRIO's default command is to start the daemon. However, it currently offers a single additional subcommand.
Outputs a commented version of the configuration file that would've been used by CRIO. This allows you to save you current configuration setup and then load it later with --config. Global options will modify the output.
--default Output the default configuration (without taking into account any configuration options).
crio.conf(5)
Sept 2016, Originally compiled by Dan Walsh dwalsh@redhat.com and Aleksa Sarai asarai@suse.de