Host Machine: Windows 10 Pro
Container image: Windows server code ltsc 2019
What am I trying to do: Access the devices connected to the host machine from the container for the purpose of uploading firmware and/or reading UART outputs.
docker run --isolation=process --device="class-forwardslash-{86E0D1E0-8089-11D0-9CE4-08003E301F73
}" mcr.microsoft.com/windows/servercore:ltsc2019
I get this error:
docker: Error response from daemon: invalid device assignment path: '.....class\{86E0D1E0-8089-11D0-9CE4-08003E301F73}', must be 'class-forwardslash-ID' or 'IDType-forwardslash-//ID'.
forwardslash= /
I have also tried it with the correct IDType and ID ( found from the device manager)
What am I doing wrong? Also, when I look for the specific GUID of my device and run it with that, I get the same error.
I know it is difficult to make this happen, but I believe with the latest changes this is now possible?
Why did you replace the “/” character with “-forwardslash-”? Assuming you had some formatting issue (added code blocks), what I ca see wrong is that you should probably not use the curly brackets at all. The documentation says
You must replace the {interface class guid} with an appropriate device interface class GUID, which can be found in the section below.
So you have to replace the whole placehlder, not just the comment between the brackets.
You might be using a solution that doesn’t fit your problem
Docker containers were developed for Linux. Docker Desktop is a developer tool, mainly to run Linux containers. (In my view)
What do you want to achieve with your solution? Isolation of the process? Have you thought about using a tool like Sandboxie or a simple VM passing USB through?
Please share the new message. It cannot be the same witha different parameter. Use code blocks when you share the error. Formatting guide is here: How to format your forum posts
