An introduction to programming with Bash.A guide to building a video game with Python.Within a container, you could put the hwdb.bin file into whichever of those locations makes the most sense to you. Openat(AT_FDCWD, "/lib/udev/hwdb.bin", O_RDONLY|O_CLOEXEC) = 3 Openat(AT_FDCWD, "/lib/systemd/hwdb/hwdb.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) Openat(AT_FDCWD, "/usr/lib/systemd/hwdb/hwdb.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) Openat(AT_FDCWD, "/etc/udev/hwdb.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) I ran lsusb under strace to find out all the locations it tries to find the hwdb.bin file from: openat(AT_FDCWD, "/etc/systemd/hwdb/hwdb.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) To keep the container as lightweight as possible, you might want to create the hwdb.bin outside the container (or use the file from your container builder host) and just inject the end product hwdb.bin into the actual container.
The hwdb.bin file is created dynamically by the systemd-hwdb update command, sourcing the information from /lib/udev/hwdb.d/*.hwdb and /etc/udev/hwdb.d/*.hwdb files. While adding the udev package to be included into the container build process is possible, it might be overkill in this case. If your container works well otherwise, it seems you only need those files for lsusb. Have /usr/share/usb.ids (and/or /lib/udev/hwdb.bin if your distribution has it) be present within the container. docker run -rm -it -privileged debian apt-get update & apt-get install -y usbutils & find / -type f \( -name "usb.ids" -o -name "hwdb.bin" means udev is not installed. Solution: usb.ids is present, but not hwdb.bin (hardware database). Virtual Mouseīus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubĪny idea how to get USB device descriptions from inside the Docker container? Virtual USB Hubīus 002 Device 002: ID 0e0f:0003 VMware, Inc.
In a Docker container: docker run -rm -it -privileged debian apt-get update & apt-get install -y usbutils & lsusbīus 002 Device 001: ID the host: $ lsusbīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 002 Device 012: ID 1a86:5512 QinHeng Electronics CH341 in EPP/MEM/I2C mode, EPP/I2C adapterīus 002 Device 003: ID 0e0f:0002 VMware, Inc.
0 kommentar(er)
