Differences Between This and Handbrake Optical Drive Scripts

[GoremanX]

Why is the script for exposing an optical drive to the image so different between this image and the Handbrake one? In this one, I need to provide both the device node itself (in this case, /dev/sr0) and the generic SCSI layer that exposes the drive (in my case, /dev/sg3, though that can change depending on how many disks are in the system). But in Handbrake, I only need to specify the device node (/dev/sr0). The script for this system appears to potentially create some issues when the generic SCSI layer changes, when it could just be dynamically detected on startup. Specifying just /dev/sr0 results in the device not being passed to the image:

[cont-init   ] 54-check-optical-drive.sh: executing...
[cont-init   ] 54-check-optical-drive.sh: looking for usable optical drives...
[cont-init   ] 54-check-optical-drive.sh: found optical drive [/dev/sr0, /dev/sg3], but it is not usable because:
[cont-init   ] 54-check-optical-drive.sh:   --> the host device /dev/sg3 is not exposed to the container.
[cont-init   ] 54-check-optical-drive.sh: no usable optical drive found.
[cont-init   ] 54-check-optical-drive.sh: terminated successfully.

Again, this doesn't appear to be an issue with the Handbrake image, and I'm confused as to why that would be.

[C4Wiz]

I would assume it has something to do with firmware access for libre drive

[jlesage]

Yes, MakeMKV needs more low-level accesses to the drive than HandBrake, which just read an existing disc without doing any decryption.