Bringing GPU acceleration to Windows containers

Published Apr 03 2019 09:10 AM 31.3K Views
Microsoft

At the release of Windows Server 2019 last year, we announced support for a set of hardware devices in Windows containers. One popular type of device missing support at the time: GPUs. We’ve heard frequent feedback that you want hardware acceleration for your Windows container workloads, so today, we’re pleased to announce the first step on that journey: starting in Windows Server 2019, we now support GPU acceleration for DirectX-based apps and frameworks in Windows containers.

 

The best part is, you can use the Windows Server 2019 build you have today—no new OS patches or configuration is necessary. All you need is a new build of Docker and the latest display drivers. Read on for detailed requirements and to learn how you can get started with GPU accelerated DirectX in Windows containers today.

 

Background: Why GPU acceleration?

 

Containers are an excellent tool for packaging and deploying many kinds of workloads. For many of these, traditional CPU compute resources are sufficient. However, for a certain class of workload, the massively parallel compute power offered by GPUs (graphics processing units) can speed up operations  by orders of magnitude, bringing down cost and improving throughput immensely.

 

GPUs are already a common tool for many popular workloads, from traditional rendering and simulation to machine learning training and inference. With today’s announcement, we’re unlocking new app scenarios for Windows containers and enabling more applications to be successfully shifted into Windows containers.

 

GPU-accelerated DirectX, Windows ML, and more

 

For some users, DirectX conjures associations with gaming. But DirectX is about more than games—it also powers a large ecosystem of multimedia, design, computation, and simulation frameworks and applications.

 

As we looked at adding GPU support to Windows containers, it was clear that starting with the DirectX APIs—the foundation of accelerated graphics, compute, and AI on Windows—was a natural first step.

 

By enabling GPU acceleration for DirectX, we’ve also enabled GPU acceleration for the frameworks built on top of it. One such framework is Windows ML, a set of APIs providing fast and efficient AI inferencing capabilities. With GPU acceleration in Windows containers, developers now have access to a first-class inferencing runtime that can be accelerated across a broad set of capable GPU acceleration hardware.overview-diagram.png

 

Usage

 

On a system meeting the requirements (see below), start a container with hardware-accelerated DirectX support by specifying the --device option at container runtime, as follows:

 

docker run --isolation process --device class/5B45201D-F2F2-4F3B-85BB-30FF1F953599 <your Docker image>

 

Note that this does not assign GPU resources exclusively to the container, nor does it prevent GPU access on the host. Rather, GPU resources are scheduled dynamically across the host and containers in much the same way as they are scheduled among apps running on your personal device today. You can have several Windows containers running on a host, each with hardware-accelerated DirectX capabilities.

 

Requirements

 

For this feature to work, your environment must meet the following requirements:

  • The container host must be running Windows Server 2019 or Windows 10, version 1809 or newer.
  • The container base image must be mcr.microsoft.com/windows:1809 or newer. Windows Server Core and Nano Server container images are not currently supported.
  • The container must be run in process isolation mode. Hyper-V isolation mode is not currently supported.
  • The container host must be running Docker Engine 19.03 or newer.
  • The container host must have a GPU running display drivers version WDDM 2.5 or newer.

To check the WDDM version of your display drivers, run the DirectX Diagnostic Tool (dxdiag.exe) on your container host. In the tool’s “Display” tab, look in the “Drivers” section as indicated below.

 

dxdiag.png

 

Getting started

 

Operating system support for this feature is already complete and broadly available as part of Windows Server 2019 and Windows 10, version 1809. Formal Docker support is scheduled for the upcoming Docker EE Engine 19.03 release. Until then, if you’re eager to try out the feature early, you can check out our sample on GitHub and follow the README instructions to get started. We’ll show you how to acquire a nightly build of Docker and use it to run a containerized Windows ML inferencing app with GPU acceleration.

 

Going forward

 

We look forward to getting your feedback on this experience. Please leave a comment below or tweet us with your thoughts. What are the next things you’d like to be able to do with GPU acceleration in containers on Windows?

 

Cheers,

Rick Manning, Graphics PM

@CraigWilhite, Windows Container PM

 

31 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-413402%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-413402%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20is%20good%20news!%20I%20would%20be%20interested%20in%20OpenGL%20and%20CUDA%20support%2C%20how%20far%20away%20is%20that%3F%20The%20main%20use%20case%20would%20be%20offscreen%2Fremote%20rendering.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-428023%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-428023%22%20slang%3D%22en-US%22%3E%3CP%3EHello.%20The%20docker%20hub%20link%20that%20you%20mention%20doesn't%20seem%20to%20work%2C%20any%20idea%20why%3F%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fhub.docker.com%2F_%2Fmicrosoft-windowsfamily-windows%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Emcr.microsoft.com%2Fwindows%3A1809%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-393939%22%20slang%3D%22en-US%22%3EBringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393939%22%20slang%3D%22en-US%22%3E%3CP%3EAt%20the%20release%20of%20Windows%20Server%202019%20last%20year%2C%20we%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FContainers%2FBringing-Device-Support-to-Windows-Containers%2Fba-p%2F382423%22%20target%3D%22_blank%22%3Eannounced%20support%20for%20a%20set%20of%20hardware%20devices%3C%2FA%3E%20in%20Windows%20containers.%20One%20popular%20type%20of%20device%20missing%20support%20at%20the%20time%3A%20GPUs.%20We%E2%80%99ve%20heard%20frequent%20feedback%20that%20you%20want%20hardware%20acceleration%20for%20your%20Windows%20container%20workloads%2C%20so%20today%2C%20we%E2%80%99re%20pleased%20to%20announce%20the%20first%20step%20on%20that%20journey%3A%20starting%20in%20Windows%20Server%202019%2C%20we%20now%20support%20GPU%20acceleration%20for%20DirectX-based%20apps%20and%20frameworks%20in%20Windows%20containers.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20best%20part%20is%2C%20you%20can%20use%20the%20Windows%20Server%202019%20build%20you%20have%20today%E2%80%94no%20new%20OS%20patches%20or%20configuration%20is%20necessary.%20All%20you%20need%20is%20a%20new%20build%20of%20Docker%20and%20the%20latest%20display%20drivers.%20Read%20on%20for%20detailed%20requirements%20and%20to%20learn%20how%20you%20can%20get%20started%20with%20GPU%20accelerated%20DirectX%20in%20Windows%20containers%20today.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%20id%3D%22toc-hId-1701960822%22%3EBackground%3A%20Why%20GPU%20acceleration%3F%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EContainers%20are%20an%20excellent%20tool%20for%20packaging%20and%20deploying%20many%20kinds%20of%20workloads.%20For%20many%20of%20these%2C%20traditional%20CPU%20compute%20resources%20are%20sufficient.%20However%2C%20for%20a%20certain%20class%20of%20workload%2C%20the%20massively%20parallel%20compute%20power%20offered%20by%20GPUs%20(graphics%20processing%20units)%20can%20speed%20up%20operations%20%26nbsp%3Bby%20orders%20of%20magnitude%2C%20bringing%20down%20cost%20and%20improving%20throughput%20immensely.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGPUs%20are%20already%20a%20common%20tool%20for%20many%20popular%20workloads%2C%20from%20traditional%20rendering%20and%20simulation%20to%20machine%20learning%20training%20and%20inference.%20With%20today%E2%80%99s%20announcement%2C%20we%E2%80%99re%20unlocking%20new%20app%20scenarios%20for%20Windows%20containers%20and%20enabling%20more%20applications%20to%20be%20successfully%20shifted%20into%20Windows%20containers.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%20id%3D%22toc-hId--850196139%22%3EGPU-accelerated%20DirectX%2C%20Windows%20ML%2C%20and%20more%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20some%20users%2C%20DirectX%20conjures%20associations%20with%20gaming.%20But%20DirectX%20is%20about%20more%20than%20games%E2%80%94it%20also%20powers%20a%20large%20ecosystem%20of%20multimedia%2C%20design%2C%20computation%2C%20and%20simulation%20frameworks%20and%20applications.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20we%20looked%20at%20adding%20GPU%20support%20to%20Windows%20containers%2C%20it%20was%20clear%20that%20starting%20with%20the%20DirectX%20APIs%E2%80%94the%20foundation%20of%20accelerated%20graphics%2C%20compute%2C%20and%20AI%20on%20Windows%E2%80%94was%20a%20natural%20first%20step.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBy%20enabling%20GPU%20acceleration%20for%20DirectX%2C%20we%E2%80%99ve%20also%20enabled%20GPU%20acceleration%20for%20the%20frameworks%20built%20on%20top%20of%20it.%20One%20such%20framework%20is%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fai%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%20ML%3C%2FA%3E%2C%20a%20set%20of%20APIs%20providing%20fast%20and%20efficient%20AI%20inferencing%20capabilities.%20With%20GPU%20acceleration%20in%20Windows%20containers%2C%20developers%20now%20have%20access%20to%20a%20first-class%20inferencing%20runtime%20that%20can%20be%20accelerated%20across%20a%20broad%20set%20of%20capable%20GPU%20acceleration%20hardware.%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20329px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F101609i41E74F37246F21EE%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22overview-diagram.png%22%20title%3D%22overview-diagram.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%20id%3D%22toc-hId-892614196%22%3EUsage%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOn%20a%20system%20meeting%20the%20requirements%20(see%20below)%2C%20start%20a%20container%20with%20hardware-accelerated%20DirectX%20support%20by%20specifying%20the%20%3CSTRONG%3E--device%3C%2FSTRONG%3E%20option%20at%20container%20runtime%2C%20as%20follows%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3Edocker%20run%20--isolation%20process%20--device%20class%2F5B45201D-F2F2-4F3B-85BB-30FF1F953599%20%26lt%3Byour%20Docker%20image%26gt%3B%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENote%20that%20this%20does%20not%20assign%20GPU%20resources%20%3CEM%3Eexclusively%3C%2FEM%3E%20to%20the%20container%2C%20nor%20does%20it%20prevent%20GPU%20access%20on%20the%20host.%20Rather%2C%20GPU%20resources%20are%20scheduled%20dynamically%20across%20the%20host%20and%20containers%20in%20much%20the%20same%20way%20as%20they%20are%20scheduled%20among%20apps%20running%20on%20your%20personal%20device%20today.%20You%20can%20have%20several%20Windows%20containers%20running%20on%20a%20host%2C%20each%20with%20hardware-accelerated%20DirectX%20capabilities.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%20id%3D%22toc-hId--1659542765%22%3ERequirements%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20this%20feature%20to%20work%2C%20your%20environment%20must%20meet%20the%20following%20requirements%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20container%20host%20must%20be%20running%20Windows%20Server%202019%20or%20Windows%2010%2C%20version%201809%20or%20newer.%3C%2FLI%3E%0A%3CLI%3EThe%20container%20base%20image%20must%20be%20%3CA%20href%3D%22https%3A%2F%2Fhub.docker.com%2F_%2Fmicrosoft-windows%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Emcr.microsoft.com%2Fwindows%3A1809%3C%2FA%3E%20or%20newer.%20Windows%20Server%20Core%20and%20Nano%20Server%20container%20images%20are%20not%20currently%20supported.%3C%2FLI%3E%0A%3CLI%3EThe%20container%20must%20be%20run%20in%20process%20isolation%20mode.%20Hyper-V%20isolation%20mode%20is%20not%20currently%20supported.%3C%2FLI%3E%0A%3CLI%3EThe%20container%20host%20must%20be%20running%20Docker%20Engine%2019.03%20or%20newer.%3C%2FLI%3E%0A%3CLI%3EThe%20container%20host%20must%20have%20a%20GPU%20running%20display%20drivers%20version%20WDDM%202.5%20or%20newer.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ETo%20check%20the%20WDDM%20version%20of%20your%20display%20drivers%2C%20run%20the%20DirectX%20Diagnostic%20Tool%20(dxdiag.exe)%20on%20your%20container%20host.%20In%20the%20tool%E2%80%99s%20%E2%80%9CDisplay%E2%80%9D%20tab%2C%20look%20in%20the%20%E2%80%9CDrivers%E2%80%9D%20section%20as%20indicated%20below.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20center%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F101610i82429FE69E753D2D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22dxdiag.png%22%20title%3D%22dxdiag.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%20id%3D%22toc-hId-83267570%22%3EGetting%20started%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOperating%20system%20support%20for%20this%20feature%20is%20already%20complete%20and%20broadly%20available%20as%20part%20of%20Windows%20Server%202019%20and%20Windows%2010%2C%20version%201809.%20Formal%20Docker%20support%20is%20scheduled%20for%20the%20upcoming%20Docker%20EE%20Engine%2019.03%20release.%20Until%20then%2C%20if%20you%E2%80%99re%20eager%20to%20try%20out%20the%20feature%20early%2C%20you%20can%20check%20out%20our%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FVirtualization-Documentation%2Ftree%2Flive%2Fwindows-container-samples%2Fdirectx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Esample%20on%20GitHub%3C%2FA%3E%20and%20follow%20the%20README%20instructions%20to%20get%20started.%20We%E2%80%99ll%20show%20you%20how%20to%20acquire%20a%20nightly%20build%20of%20Docker%20and%20use%20it%20to%20run%20a%20containerized%20Windows%20ML%20inferencing%20app%20with%20GPU%20acceleration.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%20id%3D%22toc-hId-1826077905%22%3EGoing%20forward%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20look%20forward%20to%20getting%20your%20feedback%20on%20this%20experience.%20Please%20leave%20a%20comment%20below%20or%20tweet%20us%20with%20your%20thoughts.%20What%20are%20the%20next%20things%20you%E2%80%99d%20like%20to%20be%20able%20to%20do%20with%20GPU%20acceleration%20in%20containers%20on%20Windows%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECheers%2C%3C%2FP%3E%0A%3CP%3ERick%20Manning%2C%20Graphics%20PM%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2FCraigWilhite%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%40CraigWilhite%3C%2FA%3E%2C%20Windows%20Container%20PM%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-393939%22%20slang%3D%22en-US%22%3E%3CP%3EDiscover%20how%20to%20bring%20hardware-accelerated%20DirectX%20apps%20to%20Windows%20containers%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-428589%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-428589%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F317009%22%20target%3D%22_blank%22%3E%40deltaflo%3C%2FA%3E%26nbsp%3Bthanks!%20We%20don't%20have%20a%20timeline%20yet%20for%20frameworks%20beyond%20DirectX.%20I%20get%20the%20OpenGL%20interest%20for%20remote%20rendering%3B%20how%20does%20CUDA%20fit%20into%20that%20for%20you%3F%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318532%22%20target%3D%22_blank%22%3E%40ionlucas%3C%2FA%3E%26nbsp%3Bthe%20hyperlink%20was%20broken%20but%20is%20now%20fixed.%20Thanks%20for%20catching%20that!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-429142%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-429142%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BWe%20use%20CUDA%20for%20remote%20rendering%20(interactive%20photo%20realistic%20path%20tracing)%20and%20machine%20learning%20(TensorFlow).%3C%2FP%3E%3CP%3EI%20think%20most%20machine%20learning%20people%20would%20love%20CUDA%20support.%3C%2FP%3E%3CP%3ECurrently%20one%20has%20to%20use%20linux%20with%20nvidia-docker%2C%20it%20would%20be%20great%20if%20Windows%20docker%20container%20could%20do%20the%20same.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-435007%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-435007%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F66951%22%20target%3D%22_blank%22%3E%40Craig%20Wilhite%3C%2FA%3E%2C%20does%20it%20supports%20hardware%20acceleration%20for%20video%20encoding%20with%20Microsoft%20Media%20Foundation%20and%20hardware%20acceleration%20for%20Video%20decoding%20with%20DXVA%202.0%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480713%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480713%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F256400%22%20target%3D%22_blank%22%3E%40nkef_gr%3C%2FA%3E%26nbsp%3Bwrote%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3Edoes%20it%20supports%20hardware%20acceleration%20for%20video%20encoding%20with%20Microsoft%20Media%20Foundation%20and%20hardware%20acceleration%20for%20Video%20decoding%20with%20DXVA%202.0%20%3F%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EThanks%20for%20your%20question!%20Currently%20Windows%20containers%20%3CU%3Edo%3C%2FU%3E%20support%20hardware-accelerated%20video%20decode%20using%20DXVA%2C%20but%20%3CU%3Edo%20not%3C%2FU%3E%20support%20hardware-accelerated%20video%20encode%20using%20Media%20Foundation%20Transforms.%20We're%20investigating%20enabling%20the%20latter%20in%20an%20upcoming%20release.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481036%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481036%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F257113%22%20target%3D%22_blank%22%3E%40rickman_MSFT%3C%2FA%3E%2C%20that%20are%20very%20good%20news%2C%20is%20there%20any%20time-frame%20when%20the%20hardware-accelerated%20video%20encode%20using%20Media%20Foundation%20Transforms%20will%20be%20released%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481404%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481404%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F256400%22%20target%3D%22_blank%22%3E%40nkef_gr%3C%2FA%3E%26nbsp%3Bwrote%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CSPAN%3Eis%20there%20any%20time-frame%20when%20the%20hardware-accelerated%20video%20encode%20using%20Media%20Foundation%20Transforms%20will%20be%20released%20%3F%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EUnfortunately%20I'm%20not%20able%20to%20share%20a%20timeline%20for%20this%20support%20yet%2C%20but%20we're%20actively%20investigating%20it%20and%20would%20like%20to%20enable%20it%20as%20soon%20as%20we%20can.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-683287%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-683287%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20any%20news%20about%20tensorflow%20support%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-683339%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-683339%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F338017%22%20target%3D%22_blank%22%3E%40Daniele_Bulgarelli%3C%2FA%3E%26nbsp%3Bwrote%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3EHello%2C%20any%20news%20about%20tensorflow%20support%3F%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3ETensorflow%20itself%20is%20just%20an%20ML%20framework%20that%20you%20can%20accelerate%20with%20a%20GPU%20run%20time%20as%20the%20back-end%20(so%20you%20could%2C%20for%20example%2C%20run%20Tensorflow%20right%20now%20in%20a%20Windows%20container%20and%20have%20it%20use%20the%20CPU--but%20that's%20probably%20not%20very%20interesting%20to%20you).%20In%20the%20context%20of%20running%20Tensorflow%20workloads%20on%20the%20GPU%2C%20which%20GPU%20back-end%20is%20of%20interest%20to%20you%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-683644%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-683644%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F66951%22%20target%3D%22_blank%22%3E%40Craig%20Wilhite%3C%2FA%3E%20mmh..%26nbsp%3B%20it%20will%20be%20possible%20to%20save%20model%20created%20with%20tensorflow%20in%20ONNX%2C%20after%20that%20use%20DirectML%20to%20accelerate%20the%20inference.%20It%20can%20be%20interesting.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-716021%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-716021%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F66951%22%20target%3D%22_blank%22%3E%40Craig%20Wilhite%3C%2FA%3E%26nbsp%3BHello.%20Are%20you%20providing%20GPU%20to%20the%20container%20or%20just%20doing%20some%20king%20of%20mapping%20for%20DirectX%3F%20I%20mean%20is%20GPU%20available%20inside%20container%20with%20this%20technology%3F%20For%20example%20is%20it%20possible%20to%20add%20GPU%20drivers%20to%20container%20and%20use%20specific%20API%2C%20like%20NVIDIA%20Video%20Codec%20SDK%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-717851%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-717851%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F365382%22%20target%3D%22_blank%22%3E%40Ivan_Ushakov%3C%2FA%3E%26nbsp%3Bwrote%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CSPAN%3E%40Craig%20Wilhite%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3BHello.%20Are%20you%20providing%20GPU%20to%20the%20container%20or%20just%20doing%20some%20king%20of%20mapping%20for%20DirectX%3F%20I%20mean%20is%20GPU%20available%20inside%20container%20with%20this%20technology%3F%20For%20example%20is%20it%20possible%20to%20add%20GPU%20drivers%20to%20container%20and%20use%20specific%20API%2C%20like%20NVIDIA%20Video%20Codec%20SDK%3F%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EHi%20Ivan.%20Thank%20you%20for%20your%20question.%20The%20technology%20enabling%20this%20configuration%20is%20essentially%20%22providing%20a%20GPU%20to%20the%20container%3B%22%20it's%20not%20just%20a%20DirectX%20API%20forwarding%20layer.%20As%20of%20today%20we%20only%20officially%20support%20GPU%20for%20DirectX%20inside%20a%20Windows%20container%2C%20but%20we%20understand%20there%20are%20plenty%20of%20container%20workloads%20that%20use%20non-DirectX%20APIs.%20So%20we're%20actively%20investigating%20support%20for%20those%20non-DirectX%20APIs%2C%20such%20as%20NVIDIA's%20as%20you%20mentioned.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-718200%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-718200%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F257113%22%20target%3D%22_blank%22%3E%40rickman_MSFT%3C%2FA%3EHi.%20Thank%20you%20for%20this%20explanation.%20You%20say%20%22officially%20support%20GPU%20for%20DirectX%22%2C%20so%20%22unofficially%22%20I%20could%20try%20to%20use%20this%20technology%20with%20other%20API%3F%20Or%20you%20restrict%20this%20somehow%20at%20Docker%20level%3F%20Just%20want%20to%20do%20some%20experiments%20with%20other%20API.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-718478%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-718478%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F365382%22%20target%3D%22_blank%22%3E%40Ivan_Ushakov%3C%2FA%3E%26nbsp%3Bwrote%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CSPAN%3E%22unofficially%22%20I%20could%20try%20to%20use%20this%20technology%20with%20other%20API%3F%20Or%20you%20restrict%20this%20somehow%20at%20Docker%20level%3F%20Just%20want%20to%20do%20some%20experiments%20with%20other%20API.%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%3CSPAN%3EI'm%20not%20aware%20of%20anything%20at%20the%20Docker%20or%20OS%20level%20intentionally%20restricting%20GPU%20acceleration%20with%20these%20other%20APIs%2C%20however%20I%20would%20not%20expect%20them%20to%20work.%20I%20believe%20there%20is%20missing%20OS%20and%2For%20driver%20functionality%20that%20would%20be%20required%20to%20make%20these%20work%3B%20this%20is%20the%20focus%20of%20our%20investigations%20into%20enabling%20them.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-754217%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754217%22%20slang%3D%22en-US%22%3E%3CP%3Edocker%20run%20--isolation%20process%20--device%20class%2F5B45201D-F2F2-4F3B-85BB-30FF1F953599%20winml-runner%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3Einvalid%20argument%20%22class%2F5B45201D-F2F2-4F3B-85BB-30FF1F953599%22%20for%20%22--device%22%20flag%3A%20class%2F5B45201D-F2F2-4F3B-85BB-30FF1F953599%20is%20not%20an%20absolute%20path%3CBR%20%2F%3ESee%20'docker%20run%20--help'.%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EHow%20to%20set%20the%20--device%3F%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-754941%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754941%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376220%22%20target%3D%22_blank%22%3E%40docker1575%3C%2FA%3E%26nbsp%3Bwrote%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CFONT%3Einvalid%20argument%20%22class%2F5B45201D-F2F2-4F3B-85BB-30FF1F953599%22%20for%20%22--device%22%20flag%3A%20class%2F5B45201D-F2F2-4F3B-85BB-30FF1F953599%20is%20not%20an%20absolute%20path%3CBR%20%2F%3ESee%20'docker%20run%20--help'.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%3EHow%20to%20set%20the%20--device%3F%3C%2FFONT%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EThis%20error%20occurs%20if%20you're%20not%20running%20a%20Docker%20client%2Fengine%20that%20supports%20'--device'%20arg%20for%20Windows%20containers.%20This%20functionality%20is%20not%20yet%20available%20in%20non-edge%20editions%20of%20Docker%20Desktop%20for%20Windows.%20Have%20you%20verified%20you're%20running%20the%20latest%20version%20of%20Docker%20Desktop%20for%20Windows%20%3CSTRONG%3EEdge%3C%2FSTRONG%3E%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-754987%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754987%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F66951%22%20target%3D%22_blank%22%3E%40Craig%20Wilhite%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20very%20much.%20I%20found%20the%20mistake%20and%20fixed%20it%20now.%3C%2FP%3E%3CP%3EBut%20I%20still%20met%20a%20problem%20now%2C%20When%20I%20execute%20%22%3CFONT%3Edocker%20run%20--isolation%20process%20--device%20class%2F5B45201D-F2F2-4F3B-85BB-30FF1F953599%20winml-runner%3C%2FFONT%3E%22%3C%2FP%3E%3CP%3Ethe%20powershell%20has%20no%20response.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20I%20open%20a%20new%20powershell%20window%20to%20execute%20%22docker%20ps%20-a%22%20%2C%26nbsp%3B%20The%20STATUS%20is%20Created!!%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3ECONTAINER%20ID%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20IMAGE%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20COMMAND%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20CREATED%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20STATUS%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20PORTS%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20NAMES%3CBR%20%2F%3E17efd899cf91%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20winml-runner%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%22C%3A%2FApp%2FWinMLRunner_%E2%80%A6%22%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2013%20seconds%20ago%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Created%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20mystifying_lumiere%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EAnd%20I%20execute%20%22docker%20logs%26nbsp%3B%3CFONT%3Emystifying_lumiere%3C%2FFONT%3E%22%2C%20the%20powershell%20has%20no%20response%20too.%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EWhat's%20wrong%3F%26nbsp%3B%20why%20not%20running%20status%3F%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EMy%20environment%20is%20%3A%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3EHOST%20OS%3A%20Windows%2010%20Professional%201903%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E%3CSPAN%3EThe%20container%20base%20image%3C%2FSPAN%3E%3A%26nbsp%3Bmcr.microsoft.com%2Fwindows%3A1903%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3Edocker%20version%3A%3C%2FFONT%3E%3C%2FP%3E%3CDIV%3E%3CFONT%3EClient%3A%20Docker%20Engine%20-%20Community%3CBR%20%2F%3E%26nbsp%3BVersion%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2019.03.0-rc2%3CBR%20%2F%3E%26nbsp%3BAPI%20version%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%201.40%3CBR%20%2F%3E%26nbsp%3BGo%20version%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20go1.12.5%3CBR%20%2F%3E%26nbsp%3BGit%20commit%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20f97efcc%3CBR%20%2F%3E%26nbsp%3BBuilt%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Wed%20Jun%26nbsp%3B%205%2001%3A37%3A59%202019%3CBR%20%2F%3E%26nbsp%3BOS%2FArch%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20windows%2Famd64%3CBR%20%2F%3E%26nbsp%3BExperimental%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20false%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%3EServer%3A%20Docker%20Engine%20-%20Community%3CBR%20%2F%3E%26nbsp%3BEngine%3A%3CBR%20%2F%3E%26nbsp%3B%20Version%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2019.03.0-rc2%3CBR%20%2F%3E%26nbsp%3B%20API%20version%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%201.40%20(minimum%20version%201.24)%3CBR%20%2F%3E%26nbsp%3B%20Go%20version%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20go1.12.5%3CBR%20%2F%3E%26nbsp%3B%20Git%20commit%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20f97efcc%3CBR%20%2F%3E%26nbsp%3B%20Built%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Wed%20Jun%26nbsp%3B%205%2001%3A52%3A18%202019%3CBR%20%2F%3E%26nbsp%3B%20OS%2FArch%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20windows%2Famd64%3CBR%20%2F%3E%26nbsp%3B%20Experimental%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20false%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CFONT%3EDriver%20Model%3A%202.6%20WDDM%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%3EDriver%3A%20NVIDIA%20GeForce%20GTX%201070%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-757726%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-757726%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F66951%22%20target%3D%22_blank%22%3E%40Craig%20Wilhite%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3ECould%20you%20please%20provide%20a%20baseline%20model%20inference%20tests%20on%20DirectX%20vs.%20CUDA%3F%3C%2FLI%3E%3CLI%3EOur%20code%20is%20all%20in%20%60TensorFlow%60%2C%20running%20inside%20%60nvidia-docker%60.%20Can%20you%20please%20elaborate%20on%20how%20hard%20would%20it%20be%20to%20port%20over%20the%20models%3F%3C%2FLI%3E%3C%2FOL%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-758406%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-758406%22%20slang%3D%22en-US%22%3E%3CP%3EAccording%20to%20%22Version%20compatibility%22%20below%3A%3C%2FP%3E%3CP%3E%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvirtualization%2Fwindowscontainers%2Fdeploy-containers%2Fversion-compatibility%23choose-which-container-os-version-to-use%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvirtualization%2Fwindowscontainers%2Fdeploy-containers%2Fversion-compatibility%23choose-which-container-os-version-to-use%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EIt%20supports%20process%20isolation%20only%20when%20the%20Host%20OS%20is%20windows%20server%20as%20the%20table%20below%20%2C%20Please%20make%20sure%20does%20%3CSTRONG%3E%3CFONT%20color%3D%22%23ff0000%22%3Ewindows%2010%3C%2FFONT%3E%3C%2FSTRONG%3E%20could%20support%20process%20isolation%20or%20not%3F%3F%3C%2FFONT%3E%3C%2FP%3E%3CP%3EContainer%20OS%20version%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%20Host%20OS%20version%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Compatibility%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3EWindows%20Server%202019%2C%20version%201903%3CBR%20%2F%3EBuilds%2018362.*%3C%2FTD%3E%3CTD%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23ff0000%22%3EWindows%20Server%3C%2FFONT%3E%3C%2FSTRONG%3E%2C%20version%201903%3CBR%20%2F%3EBuilds%2018362.*%3C%2FTD%3E%3CTD%3ESupports%20process%20or%20hyperv%20isolation%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EWindows%20Server%202019%3CBR%20%2F%3EBuilds%2017763.*%3C%2FTD%3E%3CTD%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23ff0000%22%3EWindows%20Server%3C%2FFONT%3E%3C%2FSTRONG%3E%202019%3CBR%20%2F%3EBuilds%2017763.*%3C%2FTD%3E%3CTD%3ESupports%20process%20or%20hyperv%20isolation%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EWindows%20Server%2C%20version%201803%3CBR%20%2F%3EBuilds%2017134.*%3C%2FTD%3E%3CTD%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23ff0000%22%3EWindows%20Server%2C%3C%2FFONT%3E%3C%2FSTRONG%3E%20version%201803%3CBR%20%2F%3EBuilds%2017134.*%3C%2FTD%3E%3CTD%3ESupports%20process%20or%20hyperv%20isolation%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EWindows%20Server%2C%20version%201709%3CBR%20%2F%3EBuilds%2016299.*%3C%2FTD%3E%3CTD%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23ff0000%22%3EWindows%20Server%3C%2FFONT%3E%3C%2FSTRONG%3E%2C%20version%201709%3CBR%20%2F%3EBuilds%2016299.*%3C%2FTD%3E%3CTD%3ESupports%20process%20or%20hyperv%20isolation%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3EWindows%20Server%202016%3CBR%20%2F%3EBuilds%3A%2014393.*%3C%2FTD%3E%3CTD%3E%3CSTRONG%3E%3CFONT%20color%3D%22%23ff0000%22%3EWindows%20Server%3C%2FFONT%3E%3C%2FSTRONG%3E%202016%3CBR%20%2F%3EBuilds%3A%2014393.*%3C%2FTD%3E%3CTD%3ESupports%20process%20or%20hyperv%20isolation%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759324%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759324%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376220%22%20target%3D%22_blank%22%3E%40docker1575%3C%2FA%3E%2C%20process%20isolation%20on%20Windows%2010%20should%20work%20for%20dev%2Ftest%20workflows.%20We%20no%20longer%20outright%20block%20process%20isolation%20mode%20on%20Windows%2010%20client%20SKUs%20in%20Docker%2C%20but%20it's%20not%20a%20production-supported%20scenario.%20The%20point%20is%2C%20everything%20described%20in%20this%20blog%20post%20should%20work%20on%20Windows%2010%20if%20you're%20running%20a%20version%201809%20or%20newer%20host%20with%20the%20latest%20Docker%20engine.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759915%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759915%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F66951%22%20target%3D%22_blank%22%3E%40Craig%20Wilhite%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20environment%20has%20met%20the%20requriements%20as%20below%2C%20but%20it%20still%20cannot%20run%20as%20your%20blog.%20%3CFONT%3EDoes%20any%20other%20settings%20need%20to%20be%20configured%3F%3F%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EHOST%20OS%3A%20Windows%2010%20Professional%201903%2018362.30%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E%3CSPAN%3EThe%20container%20base%20image%3C%2FSPAN%3E%3A%26nbsp%3Bmcr.microsoft.com%2Fwindows%3A1903%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3Edocker%20version%3A%3C%2FFONT%3E%3C%2FP%3E%3CDIV%3E%3CFONT%3EClient%3A%20Docker%20Engine%20-%20Community%3CBR%20%2F%3E%26nbsp%3BVersion%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2019.03.0-rc2%3CBR%20%2F%3E%26nbsp%3BAPI%20version%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%201.40%3CBR%20%2F%3E%26nbsp%3BGo%20version%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20go1.12.5%3CBR%20%2F%3E%26nbsp%3BGit%20commit%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20f97efcc%3CBR%20%2F%3E%26nbsp%3BBuilt%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Wed%20Jun%26nbsp%3B%205%2001%3A37%3A59%202019%3CBR%20%2F%3E%26nbsp%3BOS%2FArch%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20windows%2Famd64%3CBR%20%2F%3E%26nbsp%3BExperimental%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20false%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%3EServer%3A%20Docker%20Engine%20-%20Community%3CBR%20%2F%3E%26nbsp%3BEngine%3A%3CBR%20%2F%3E%26nbsp%3B%20Version%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2019.03.0-rc2%3CBR%20%2F%3E%26nbsp%3B%20API%20version%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%201.40%20(minimum%20version%201.24)%3CBR%20%2F%3E%26nbsp%3B%20Go%20version%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20go1.12.5%3CBR%20%2F%3E%26nbsp%3B%20Git%20commit%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20f97efcc%3CBR%20%2F%3E%26nbsp%3B%20Built%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Wed%20Jun%26nbsp%3B%205%2001%3A52%3A18%202019%3CBR%20%2F%3E%26nbsp%3B%20OS%2FArch%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20windows%2Famd64%3CBR%20%2F%3E%26nbsp%3B%20Experimental%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20false%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CFONT%3EDriver%20Model%3A%202.6%20WDDM%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%3EDriver%3A%20NVIDIA%20GeForce%20GTX%201070%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-765650%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-765650%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F377259%22%20target%3D%22_blank%22%3E%40statikk%3C%2FA%3E%26nbsp%3Bwrote%3A%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E1.%20Could%20you%20please%20provide%20a%20baseline%20model%20inference%20tests%20on%20DirectX%20vs.%20CUDA%3F%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EAre%20you%20asking%20about%20a%20performance%20comparison%20between%20DirectX%20and%20CUDA%3F%20Performance%20depends%20on%20a%20number%20of%20different%20factors%20(the%20model%20being%20evaluated%2C%20input%20types%2C%20device%20hardware%2C%20graphics%20drivers%2C%20etc.)%20so%20results%20tend%20to%20be%20specific%20to%20a%20developer's%20unique%20scenario.%20However%2C%20the%20developers%20behind%20DirectX%20and%20the%20Windows%20AI%20stack%20(WinML%2C%20DirectML%2C%20and%20related%20technologies)%20work%20extremely%20closely%20with%20hardware%20vendors%20to%20ensure%20consistent%20results%20and%20performance%20across%20the%20broad%20range%20of%20Windows%20devices%20and%20GPUs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F377259%22%20target%3D%22_blank%22%3E%40statikk%3C%2FA%3E%26nbsp%3Bwrote%3A%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E2.%20Our%20code%20is%20all%20in%20%60TensorFlow%60%2C%20running%20inside%20%60nvidia-docker%60.%20Can%20you%20please%20elaborate%20on%20how%20hard%20would%20it%20be%20to%20port%20over%20the%20models%3F%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EAgain%2C%20this%20depends%20on%20the%20details%20of%20your%20unique%20situation%2C%20but%20Microsoft%20does%20provide%20tools%20for%20porting%20models%20to%20ONNX%2C%20the%20Open%20Neural%20Network%20Exchange%20format.%20You%20can%20learn%20more%20about%20model%20conversion%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fai%2Fwindows-ml%2Fconvert-model-winmltools%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EConvert%20ML%20models%20to%20ONNX%20with%20WinMLTools%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-772707%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-772707%22%20slang%3D%22en-US%22%3E%3CP%3EDoes%20it%20support%20to%20install%20NVIDIA%20Driver%20in%20the%20container%20to%20using%20NVIDIA%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-773832%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-773832%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376220%22%20target%3D%22_blank%22%3E%40docker1575%3C%2FA%3E%26nbsp%3Bwrote%3A%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CSPAN%3EDoes%20it%20support%20to%20install%20NVIDIA%20Driver%20in%20the%20container%20to%20using%20NVIDIA%3F%3F%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EThanks%20for%20your%20question.%20I%20can%20see%20two%20possible%20ways%20to%20interpret%20your%20question%2C%20so%20I%20will%20answer%20both%20interpretations%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E1.%20Does%20this%20enable%20my%20Windows%20containers%20to%20get%20hardware%20acceleration%20on%20NVIDIA%20GPUs%3F%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EYes.%20If%20you%20have%20NVIDIA%20drivers%20installed%20on%20the%20container%20host%20(that%20meet%20the%20requirements%20described%20in%20the%20blog%20post)%2C%20then%20when%20you%20run%20a%20container%20with%20the%20%3CSTRONG%3E--device%3C%2FSTRONG%3E%26nbsp%3Bparameter%20as%20described%20in%20the%20blog%20post%2C%20your%20apps%20can%20get%20hardware%20acceleration%20whenever%20they%20use%20the%20DirectX%20graphics%20and%20compute%20APIs%20inside%20the%20container.%20You%20don't%20even%20need%20to%20install%20those%20drivers%20in%20the%20container%3B%20Docker%20automatically%20makes%20the%20right%20drivers%20from%20the%20host%20available%20to%20the%20container.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E2.%20Does%20this%20enable%20my%20Windows%20containers%20to%20get%20hardware-accelerated%20CUDA%3F%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3ENo.%20Hardware%20acceleration%20is%20currently%20only%20supported%20for%20the%20DirectX%20APIs%20(and%20higher-level%20APIs%20built%20on%20DirectX)%20but%20does%20not%20include%20CUDA%20or%20similar%20APIs.%20We've%20heard%20lots%20of%20feedback%20that%20customers%20are%20interested%20in%20those%2C%20and%20we're%20actively%20investigating%20support%20for%20those.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-785341%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-785341%22%20slang%3D%22en-US%22%3E%3CP%3EI%20second%20the%20need%20to%20support%20CUDA%20in%20docker.%20Our%20researchers%20need%20to%20accelerate%20machine%20learning%20code%20written%20e.g.%20in%20tensorflow%20using%20CUDA%2C%20or%20run%20scientific%20simulations%20that%20use%20the%20GPU.%20It%20would%20be%20great%20if%20CUDA%20and%20GPU%20passthrough%20could%20be%20supported%20in%20docker%20and%20in%20WSL%202.%20Currently%20we%20are%20forced%20to%20used%20linux%20because%20of%20this%2C%20but%20would%20prefer%20to%20use%20Windows%20Server%2C%20if%20GPU%20passthrough%20becomes%20possible.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-809102%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-809102%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20great%20work!%3CBR%20%2F%3EThis%20is%20really%20exciting!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-812177%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-812177%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F66951%22%20target%3D%22_blank%22%3E%40Craig%20Wilhite%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F257113%22%20target%3D%22_blank%22%3E%40rickman_MSFT%3C%2FA%3E%20May%20I%20ask%20a%20question%3F%3CBR%20%2F%3EIs%20it%20possible%20to%20launch%20such%20GPU%20accelerated%20Windows%20containers%20via%20Kubernetes%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKubernetes%20seems%20to%20launch%20containers%20already%20in%20process%20isolation%20mode%2C%20corresponding%20to%20the%20%3CFONT%20face%3D%22courier%20new%2Ccourier%22%3E--isolation%20process%3C%2FFONT%3E%20option%20you%20are%20mentioning%20in%20the%20article.%20But%20what%20is%20the%20Kubernetes%20equivalent%20of%20the%20%3CFONT%20face%3D%22courier%20new%2Ccourier%22%3E--device%20class%2F5B45201D-F2F2-4F3B-85BB-30FF1F953599%3C%2FFONT%3E%20option%3F%20We%20see%20no%20need%20for%20a%20Kubernetes%20device%20plugin%2C%20which%20seems%20to%20be%20the%20wrong%20way%20anyway%2C%20since%20it%20would%20assign%20GPU%20resources%20exclusively%20to%20a%20container.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20can%20successfully%20run%20our%20application%20in%20a%20GPU%20accelerated%20Windows%20container%20via%20%3CFONT%20face%3D%22courier%20new%2Ccourier%22%3Edocker%20run%3C%2FFONT%3E.%20We%20can%20also%20create%20Windows%20containers%20via%20Kubernetes%2C%20but%20without%20GPU%20access%20yet.%20Optimistically%20hoping%20that%20it%20is%20only%20a%20small%20thing%20we%20are%20missing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-828329%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-828329%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F393756%22%20target%3D%22_blank%22%3E%40Thomasin%3C%2FA%3E%26nbsp%3Bsaid%3A%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CSPAN%3EIs%20it%20possible%20to%20launch%20such%20GPU%20accelerated%20Windows%20containers%20via%20Kubernetes%3F%3C%2FSPAN%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%3CSPAN%3EUnfortunately%2C%20Kubernetes%20does%20not%20yet%20support%20resource%20allocation%20and%20enablement%20of%20GPU%20acceleration%20for%20Windows%20containers.%20It's%20something%20we're%20actively%20looking%20into%2C%20however%2C%20as%20we%20know%20many%20container%20customers%20prefer%20to%20deploy%20their%20containers%20using%20Kubernetes.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-838571%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-838571%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F257113%22%20target%3D%22_blank%22%3E%40rickman_MSFT%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20reply.%20This%20sounds%20very%20promising!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20just%20saw%20that%20this%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Faarnaud%2Fk8s-directx-device-plugin%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EDirectX%20device%20plugin%20for%20Kubernetes%3C%2FA%3E%20seems%20to%20solve%20the%20problem%2C%20but%20requires%20the%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fkubernetes%2Fkubernetes%2Fpull%2F80917%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Epending%20pull%20request%20for%20supporting%20device%20plugins%20under%20Windows%3C%2FA%3E.%20In%20contrary%20to%20my%20previous%20post%2C%20I%20now%20think%20that%20a%20device%20plugin%20is%20the%20right%20approach%2C%20and%20this%20particular%20implementation%20looks%20good%20to%20me.%20What%20do%20you%20think%20about%20it%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EMaybe%20Microsoft%20can%20throw%20in%20its%20weight%20and%20support%20the%20acceptance%20of%20that%20pull%20request%3F%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1898553%22%20slang%3D%22en-US%22%3ERe%3A%20Bringing%20GPU%20acceleration%20to%20Windows%20containers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1898553%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%26gt%3B%26gt%3B%20invalid%20argument%20%22class%2F5B45201D-F2F2-4F3B-85BB-30FF1F953599%22%20for%20%22--device%22%20flag%3A%20class%2F5B45201D-F2F2-4F3B-85BB-30FF1F953599%20is%20not%20an%20absolute%20path%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20am%20getting%20this%20same%20error%20running%20Docker%20v19.03.13%20on%20Windows%2010.%20I%20have%20enabled%20experimental%20features%20both%20in%20the%20%22Experimental%20Features%22%20section%20of%20the%20settings%20as%20well%20as%20enabling%20the%20%22experimental%22%20flag%20in%20the%20Docker%20engine.%20Not%20sure%20what%20I'm%20doing%20wrong%20here.%20Any%20tips%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Apr 10 2019 08:11 AM
Updated by:
www.000webhost.com