The current version of the OCI runtime spec states that:
-
path (string, REQUIRED) Specifies the path to the root filesystem for the container.
-
On Windows, path MUST be a [volume GUID path][naming-a-volume].
-
On POSIX platforms, path is either an absolute path or a relative path to the bundle.
For example, with a bundle at /to/bundle and a root filesystem at /to/bundle/rootfs, the path value can be either /to/bundle/rootfs or rootfs.
The value SHOULD be the conventional rootfs.
A directory MUST exist at the path declared by the field.
The current containerd architecture requires that the runtime mounts the filesystem on the host, and it is not already mounted.
On Windows, mounting the filesystem consists of creating and mounting the VHD which Root.Path must point to.
These requirements conflict. Either the runtime spec needs to allow runtimes to not require a Root.Path on Windows, or containerd needs to allow (require?) the filesystem to be mounted
cc @jhowardmsft @jstarks
The current version of the OCI runtime spec states that:
path(string, REQUIRED) Specifies the path to the root filesystem for the container.On Windows,
pathMUST be a [volume GUID path][naming-a-volume].On POSIX platforms,
pathis either an absolute path or a relative path to the bundle.For example, with a bundle at
/to/bundleand a root filesystem at/to/bundle/rootfs, thepathvalue can be either/to/bundle/rootfsorrootfs.The value SHOULD be the conventional
rootfs.A directory MUST exist at the path declared by the field.
The current containerd architecture requires that the runtime mounts the filesystem on the host, and it is not already mounted.
On Windows, mounting the filesystem consists of creating and mounting the VHD which
Root.Pathmust point to.These requirements conflict. Either the runtime spec needs to allow runtimes to not require a Root.Path on Windows, or containerd needs to allow (require?) the filesystem to be mounted
cc @jhowardmsft @jstarks