Add type field for mounts

This change adds a type field for mounts to the CDI spec. This is required
to allow for non-bind mounts (e.g. tmpfs) in the OCI runtime spec.

Signed-off-by: Evan Lezar <[email protected]>

Author: elezar

README.md

@@ -48,7 +48,8 @@ $ cat > /etc/cdi/vendor.json <<EOF
     ],
     "mounts": [
       {"hostPath": "/bin/vendorBin", "containerPath": "/bin/vendorBin"},
-      {"hostPath": "/usr/lib/libVendor.so.0", "containerPath": "/usr/lib/libVendor.so.0"}
+      {"hostPath": "/usr/lib/libVendor.so.0", "containerPath": "/usr/lib/libVendor.so.0"},
+      {"hostPath": "tmpfs", "containerPath": "/tmp/data", "type": "tmpfs", "options": ["nosuid","strictatime","mode=755","size=65536k"]}
     ],
     "hooks": [
       {"createContainer": {"path": "/bin/vendor-hook"} },

SPEC.md

@@ -111,7 +111,8 @@ The key words "must", "must not", "required", "shall", "shall not", "should", "s
                 {
                     "hostPath": "<source>",
                     "containerPath": "<destination>",
-                    "options": "<OCI Mount Options>", (optional)
+                    "type": "<OCI Mount Type>", (optional)
+                    "options": "<OCI Mount Options>" (optional)
                 }
             ],
             "hooks": [ (optional)
@@ -183,6 +184,7 @@ The `containerEdits` field has the following definition:
   * `mounts` (array of objects, OPTIONAL) describes the mounts that should be mounted:
     * `hostPath` (string, REQUIRED) path of the device on the host.
     * `containerPath` (string, REQUIRED) path of the device within the container.
+    * `type` (string, OPTIONAL) the type of the filesystem to be mounted. For bind mounts (when options include either bind or rbind), the type is a dummy, often "none" (not listed in /proc/filesystems).
     * `options` (array of strings, OPTIONAL) Mount options of the filesystem to be used.
   * `hooks` (array of objects, OPTIONAL) describes the hooks that should be ran:
     * `hookName` is the name of the hook to invoke, if the runtime is OCI compliant it should be one of {createRuntime, createContainer, startContainer, poststart, poststop}.

pkg/cdi/spec_test.go

@@ -293,6 +293,29 @@ devices:
     containerEdits:
       env:
         - "FOO=BAR"
+`,
+			vendor: "vendor.com",
+			class:  "device",
+		},
+		{
+			name:     "valid",
+			priority: 1,
+			data: `
+cdiVersion: "0.4.0"
+kind: vendor.com/device
+devices:
+  - name: "dev1"
+    containerEdits:
+      mounts:
+        - hostPath: "tmpfs"
+          containerPath: "/usr/local/container"
+          type: "tmpfs"
+          options:
+            - "ro"
+            - "mode=755"
+            - "size=65536k"
+      env:
+        - "FOO=BAR"
 `,
 			vendor: "vendor.com",
 			class:  "device",

schema/defs.json

@@ -63,6 +63,9 @@
                 },
                 "options": {
                     "$ref": "#/definitions/ArrayOfStrings"
+                },
+                "type": {
+                    "type": "string"
                 }
             },
             "required": [

specs-go/config.go

@@ -45,6 +45,7 @@ type Mount struct {
 	HostPath      string   `json:"hostPath"`
 	ContainerPath string   `json:"containerPath"`
 	Options       []string `json:"options,omitempty"`
+	Type          string   `json:"type,omitempty"`
 }
 
 // Hook represents a hook that needs to be added to the OCI spec.

specs-go/oci.go

@@ -95,6 +95,7 @@ func (m *Mount) ToOCI() spec.Mount {
 		Source:      m.HostPath,
 		Destination: m.ContainerPath,
 		Options:     m.Options,
+		Type:        m.Type,
 	}
 }