For a better experience, please enable JavaScript in your browser before proceeding.

I passthrough my devices with this command: qm set VMID -usb0 hostDEVICEID Here is lsusb twice LabelWriter 450.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub.

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub.

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub.

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub.

Bus 001 Device 009: ID 03f0:1e17 Hewlett-Packard LaserJet 1160 series.

Tens of thousands of happy customers have a Proxmox subscription.

By continuing to use this site, you are consenting to our use of cookies.

However, it doesnt mean the container can mingle with the device just yet.

So first we need to locate the device we want to pass through.

Note: lsusb will not work inside the container because there are no devices there yet Here is the output of my case: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 013: ID 045e:0800 Microsoft Corp.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub In my cas e, I want to pass through my Canon MP printer to the container.

The bus and device numbers are what we are looking for now, they can guide us to the correct device path beneath dev.

How to mount the container with this path we can do it via the lxc.mount.entry option.

We can do it via cgroup, more specifically option lxc.cgroup.device.allow.

To use this option we need to know the devices major and minor numbers which can be retrieved as follows: ls -al devbususb001020 I got: crw-rw-r 1 root lp 189, 19 Jul 10 17:32 001020 The major and minor numbers are 189 and 19 respectively.

Start the configuration In my case, I use Proxmox to manage my containers.

I need to go to etcpvelxc.conf.

I will have to put two lines more into the configuration file: lxc.cgroup.devices.allow: c 189: rwm lxc.mount.entry: devbususb001020 devbususb001020 none bind,optional,createfile The former is for allowing the container privilege to access the device specified by its major and minor numbers.

Note: 189: means we care only the major number, all the minors apply.

The latter is for mounting the device file representation into the container space.

In this case, I mount the exact device, however, it might be a good idea to map the whole directory (with all its siblings) to the container because it is more than likely that the filename will change.

Given that it can be done thus: lxc.mount.entry: devbususb001 devbususb001 none bind,optional,createdir Note: the target mount path doesnt begin with a slash it is dev not dev Now, stop and start the container.

You should now be able to run the command lsusb inside the container and see the same results as if in the host.

Konpat Ta Preechakul A graduate student in Machine Learning seeking revolutionary intelligent machines Follow 6 1 6 6 1 Lxc Proxmox More from Konpat Ta Preechakul Follow A graduate student in Machine Learning seeking revolutionary intelligent machines More From Medium Backup Restore Docker Named Volumes Jarek Lipski Running Debian Linux on Android device natively The Quantified VC Meet The Disruptors: Alan Duric of Wire On The Three Things You Need To Shake Up Your Industry Jason Hartman in Authority Magazine SSH Reverse Proxy and Tunneling Dominik Tarnowski in Better Programming How to enable IPv6 for Docker containers on Ubuntu 18.04 Stefan Kleeschulte Benchmarking the Raspberry Pi 3 B Gareth Halfacree Demystifying ARM TrustZone for Microcontrollers (and a Note on Rust Support) Nihal Pasham in The Startup How to make proxmox cry Maruan Boukhirss About Help Legal Get the Medium app.

Proxmox Serial Port Pass Through Doors