From bef035ce491180acd52b4b27da965ddd302b8108 Mon Sep 17 00:00:00 2001 From: "Rob Dolin (MSFT)" Date: Wed, 18 May 2016 11:04:55 -0700 Subject: [PATCH] [Config] Mount destinations MUST NOT be nested in Windows This was raised during reviews with folks working on Windows Containers. This squashes commits from PR #433 Signed-off-by: Rob Dolin --- config.md | 1 + 1 file changed, 1 insertion(+) diff --git a/config.md b/config.md index 5d88b2e7f..a7cfa8430 100644 --- a/config.md +++ b/config.md @@ -44,6 +44,7 @@ The runtime MUST mount entries in the listed order. The parameters are similar to the ones in [the Linux mount system call](http://man7.org/linux/man-pages/man2/mount.2.html). * **`destination`** (string, required) Destination of mount point: path inside container. +For the Windows operating system, one mount destination MUST NOT be nested within another mount. (Ex: c:\\foo and c:\\foo\\bar). * **`type`** (string, required) Linux, *filesystemtype* argument supported by the kernel are listed in */proc/filesystems* (e.g., "minix", "ext2", "ext3", "jfs", "xfs", "reiserfs", "msdos", "proc", "nfs", "iso9660"). Windows: ntfs * **`source`** (string, required) a device name, but can also be a directory name or a dummy. Windows, the volume name that is the target of the mount point. \\?\Volume\{GUID}\ (on Windows source is called target) * **`options`** (list of strings, optional) in the fstab format [https://wiki.archlinux.org/index.php/Fstab](https://wiki.archlinux.org/index.php/Fstab).