Admins can specify which named pipes users can mount with windows containers

Signed-off-by: Guillaume Tardif <guillaume.tardif@docker.com>
This commit is contained in:
Guillaume Tardif
2019-06-04 17:03:05 +02:00
parent fac42994ec
commit eb55fdb6f2

View File

@@ -143,7 +143,7 @@ The following `admin-settings.json` code and table provide the required syntax a
"locked": true,
"value": [ ]
},
"sharedFolders": ["%USERPROFILE%"]
"sharedFolders": ["%USERPROFILE%", "\\\\.\\pipe\\docker_engine"]
}
```
@@ -179,4 +179,4 @@ Parameter values and descriptions for environment configuration on Windows:
| `serviceCIDR` | This is currently unimplemented. `locked` must be set to true. |
| (End of `kubernetes` section.) | |
| `sharedDrives` | If `sharedDrives` is set to `true`, this locks the drives users are allowed to share ( `["C", "D"]` ), but does not actually share drives by default (sharing a drive prompts the user for a password). `value` is a whitelist of drives that can be shared. **Warning:** Note that when updating this value, if you remove drives that have been shared, you must also `net share /delete` those drives. |
| `sharedFolders` | If specified, restrict the folders the user is allowed to share with Windows containers. |
| `sharedFolders` | If specified, restrict the folders or named pipes the user is allowed to share with Windows containers. |