


I think my drive doesn't support makemkv. Installation The software MakeMKV is available for installation on Linux, Windows and macOS. I ran makemkvcon from hypervisor to guest to container and none of them worked. Any ideas or should I open a bug with MakeMKV? My optical drive is this one here. I don't know how to verify that cont-init.d picked up my drives, but I'm able to see both devices in my /dev/ folder. I'm able to verify the contents of my DVD in the Proxmox guest and the container by mounting them. You're letting the computer beat you! FYI, this issue still exists.

I don't think of buying new hardware as an easy win, generally. I am closing this issue, but hopefully if anyone else encounters this problem with an internal DVD drive it will lead them towards trying a USB DVD drive and potentially seeing an easy win. As such, I am forced to conclude that the issue was either a problem with that internal DVD drive or with the way Proxmox was passing it through. I have bought a USB Blu-Ray drive, and that is picked up just fine by the MakeMkv Docker container after that specific USB device is passed through to the Ubuntu server VM in Proxmox.
