Add docs for --device option in Windows#1663
Add docs for --device option in Windows#1663thaJeztah merged 1 commit intodocker:masterfrom cwilhit:crwilhit-WindowsDocs-Update
Conversation
docs/reference/commandline/run.md
Outdated
There was a problem hiding this comment.
Rather than Today, perhaps state what versions of Windows. (AFAIK, this is RS5/1809 on only).
Codecov Report
@@ Coverage Diff @@
## master #1663 +/- ##
==========================================
+ Coverage 56.12% 56.13% +<.01%
==========================================
Files 306 306
Lines 20964 20931 -33
==========================================
- Hits 11766 11749 -17
+ Misses 8345 8334 -11
+ Partials 853 848 -5 |
lowenna
left a comment
There was a problem hiding this comment.
LGTM (not a maintainer in this repo)
thaJeztah
left a comment
There was a problem hiding this comment.
Thanks! I left some suggestions below (feel free to amend your commits to use those). Could you also squash your commits, so that there's only a single commit in this pull request? Let me know if you need help doing so 👍
docs/reference/commandline/run.md
Outdated
There was a problem hiding this comment.
Trying to avoid "please" in the documentation; perhaps
Refer to the table defined in the [Windows container
documentation](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/hardware-devices-in-containers)
for a list of container-supported device interface class GUIDs.Also, could you wrap these to ~80 chars?
| For Windows, the format of the string passed to the `--device` option is in the form of `--device=<IdType>/<Id>`. Beginning with Windows Server 2019 and Windows 10 October 2018 Update, Windows only supports an IdType of `class` and the Id as a [device interface class GUID](https://docs.microsoft.com/en-us/windows-hardware/drivers/install/overview-of-device-interface-classes). For a list of container-supported device interface class GUIDs, please refer to the table defined in the [Windows container docs](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/hardware-devices-in-containers). | |
| For Windows, the format of the string passed to the `--device` option is in | |
| the form of `--device=<IdType>/<Id>`. Beginning with Windows Server 2019 | |
| and Windows 10 October 2018 Update, Windows only supports an IdType of | |
| `class` and the Id as a [device interface class | |
| GUID](https://docs.microsoft.com/en-us/windows-hardware/drivers/install/overview-of-device-interface-classes). | |
| Refer to the table defined in the [Windows container | |
| documentation](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/hardware-devices-in-containers) | |
| for a list of container-supported device interface class GUIDs. |
There was a problem hiding this comment.
Thanks, added these fixes.
docs/reference/commandline/run.md
Outdated
There was a problem hiding this comment.
Should it be "devices that implement" (instead of "which"?)
Also, try to avoid future tense in technical documentation; here's a quick go at changing it to remove the future tense, and wrap the paragraph to 80 chars;
| When this option is specified for a process-isolated Windows container, _all_ devices which implement the requested device interface class GUID will be made available in the container. For example, the command below will make all COM ports on the host visibile in the container. | |
| If this option is specified for a process-isolated Windows container, _all_ | |
| devices that implement the requested device interface class GUID are made | |
| available in the container. For example, the command below makes all COM | |
| ports on the host visible in the container. |
There was a problem hiding this comment.
You are correct--I've now learned when to use 'which' vs 'that'. It always confounded me in the past.
docs/reference/commandline/run.md
Outdated
There was a problem hiding this comment.
Slightly changed to wrap to 80-chars, and remove future tense;
| > **Note**: `--device` may only be used on Windows with process-isolated Windows containers. This option will fail if the container | |
| > **Note**: the `--device` option is only supported on process-isolated | |
| > Windows containers. This option fails if the container isolation is `hyperv` | |
| > or when running Linux Containers on Windows (LCOW). |
|
@thaJeztah Ok, incorporated the changes. This is the first time I've squashed commits before, but I believe I got it correctly. Per instructions online, I had to force push to my branch on Github. |
silvin-lubecki
left a comment
There was a problem hiding this comment.
LGTM, thank you for this contribution @cwilhit 👍
thaJeztah
left a comment
There was a problem hiding this comment.
spotted two markdown issues, but LGTM otherwise, so ok to merge after those are addressed (thanks!)
docs/reference/commandline/run.md
Outdated
There was a problem hiding this comment.
oh; the URL itself cannot be wrapped (it's ok for the caption, but not for the URL)
docs/reference/commandline/run.md
Outdated
…mitations (no Hyper-V isolation, no LCOW). Signed-off-by: Craig Wilhite <crwilhit@microsoft.com>
Signed-off-by: Craig Wilhite crwilhit@microsoft.com
Adds documentation portion for #1606. Includes a reference for how to run with --device on Windows & explain limitations of the feature (no Hyper-V isolation, no LCOW).
@jhowardmsft FYI