But for some reason, why I tell the docker to look at that path, it does not recognize the device. Inside the specific docker I'm looking at, without any type of mapping, if I docker exec /bin/bash into it, I can navigate to /dev/bus/usb and find the same lists of devices. I see a a few posts mentioning /dev/ttyUSB0 or /dev/ttyS0, but I don't know what the connection is. I can find the specific path of this USB device on /dev/bus/usb/001/007. This changes if I unplug and replug, but that's a problem for another day. The device I need to pass through is on Bus 001 and is Device 007. Integrated Rate Matching Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Integrated Rate Matching Hubīus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 001 Device 004: ID 0781:5571 SanDisk Corp. When I run command lsusb on my unRAID console, I get:īus 002 Device 002: ID 8087:0024 Intel Corp. The one I'm using in this case is Home-Assistant.įor starters, I have located the proper USB device on my unRAID hardware. I imagine this would be the same process for any docker needing to see a USB device. From there, I would like the container to be able to read from this Z-Wave Stick. I originally posted this on a specific container support thread, but realized this is specific to the usage of docker in general, not the specific container I was using.įor transparency, I'm attempting to attach my Z-Wave stick to my unRAID console.