Adding cgroups path to the Spec.

vishh · vishh · commit be6ec5ff5eb0 · 2015-09-02T14:59:18.000-07:00
Signed-off-by: Vishnu Kannan &lt;vishnuk@google.com&gt;
diff --git a/runtime-config-linux.md b/runtime-config-linux.md
@@ -130,6 +130,13 @@ Next parameters can be specified:
 Also known as cgroups, they are used to restrict resource usage for a container and handle
 device access.  cgroups provide controls to restrict cpu, memory, IO, and network for
 the container. For more information, see the [kernel cgroups documentation](https://www.kernel.org/doc/Documentation/cgroups/cgroups.txt).
+The path to the cgroups can be specified in the Spec. The path is expected to be relative
+to the cgroups mount point. The Spec does not support split hierarchy. The cgroups will be 
+created if they don't exist. 
+
+```json
+   "cgroupsPath": "/myRuntime/myContainer"
+```
 
 ## Sysctl
 
diff --git a/runtime_config_linux.go b/runtime_config_linux.go
@@ -21,6 +21,9 @@ type LinuxRuntime struct {
 	// Resources contain cgroup information for handling resource constraints
 	// for the container
 	Resources Resources `json:"resources"`
+	// CgroupsPath specifies the path to cgroups that are created and/or joined by the container.
+	// The path is expected to be relative to the cgroups mountpoint.
+	CgroupsPath string `json:"cgroupsPath"`
 	// Namespaces contains the namespaces that are created and/or joined by the container
 	Namespaces []Namespace `json:"namespaces"`
 	// Devices are a list of device nodes that are created and enabled for the container
