Description for getting MakeMKV working on Synology with DSM 7 using jlesage/makemkv via Docker Compose

99-usb-cdrom.rules

SUBSYSTEMS=="usb", ATTRS{idVendor}=="", ATTRS{idProduct}=="", GROUP="cdrom", MODE="0666"

docker-compose.yml

version: '3'

services:
  makemkv:
    image: jlesage/makemkv:latest
    container_name: makemkv
    restart: unless-stopped
    network_mode: bridge
    ports:
      - "5800:5800"
    environment:
      MAKEMKV_KEY: <redacted>
      USER_ID: 1026
      GROUP_ID: 101
      AUTO_DISC_RIPPER: 1
      APP_NICENESS: 19
    volumes:
      - "/volume1/Docker/makemkv/config:/config:rw"
      - "/volume1/Downloads:/storage:ro"
      - "/volume1/Media:/output:rw"
    devices:
      - "/dev/sg6:/dev/sg6"

procedure.md

These are the steps I used to get MakeMKV working from Docker on my Synology NAS (DS1520+).

In my setup, I have a shared folder for Media, for Downloads, and for Docker-related files. Amend these steps for your own purposes by using directories which exist on your NAS. My USB Blu-ray drive is a Pioneer BDR-XD05B.

1. Enable SSH if needed.
2. SSH to the Synology NAS.
3. Connect USB CD-ROM drive to the physical NAS.
4. Use dmesg to see which SCSI device was created.
   • In my case, it was sg6, so I knew that the device was created at /dev/sg6. Adjust as needed for your own purposes.
5. Create the needed directories: mkdir -p /volume1/Docker/makemkv/config
6. Copy docker-compose.yml from below to /volume1/Docker/makemkv.
   • Adjust any directory names if needed.
   • Adjust the name of the SCSI device if needed.
   • Adjust the MAKEMKV_KEY environment variable value to contain your key.
   • Adjust any other environment variables needed. See documentation.
7. Copy 99-usb-cdrom.rules from below to /lib/udev/rules.d/. (Requires root permissions with sudo.)
   • At this time, you should also chmod 0666 /dev/sg6 (or whichever device you have) so that you don't have to reboot to apply the necessary permissions. (Requires root permissions with sudo.)
8. Change directory: cd /volume1/Docker/makemkv.
9. Create the container: docker-compose up -d.
10. Access MakeMKV on your Synology unit at http://<synology>:5800/.
    • You can either open up port 5800 in the firewall settings in DSM, or you can set up a reverse proxy configuration to access it securely. Both methods are outside the scope of this procedure.

Thank you very much I now have the container up and running.

Everything is working except auto eject. I had previously created makemkv in a VM on Synology including auto eject. The only difference I can see is that inside the VM, the container is looking for two optical drive devices which are present (sr2 and sg3) but outside the VM with the container running in Synology Container Manager it is only looking for one (sg5).

Do you have autoeject operating?

Thank you very much I now have the container up and running.

I'm so glad I could be helpful!

Everything is working except auto eject. I had previously created makemkv in a VM on Synology including auto eject. The only difference I can see is that inside the VM, the container is looking for two optical drive devices which are present (sr2 and sg3) but outside the VM with the container running in Synology Container Manager it is only looking for one (sg5).

Do you have autoeject operating?

I wrote this almost three years ago and then promptly forgot about it until your comment. I'm afraid I don't remember, and I probably did not get auto-eject working. Sorry. Feel free to follow up if you do get that working as well.

hey emilyst.

Thank you for the write up.

I did exactly what you've written (3 times) but I can't get my Pioneer drive working.

compose file:

version: '3'

services:
  makemkv:
    image: jlesage/makemkv:latest
    container_name: makemkv-disc
    restart: unless-stopped
    network_mode: bridge
    ports:
      - "xxxx0:5900"
      - "xxxx1:5800"
    environment:
      MAKEMKV_KEY: *****mykey*****
      USER_ID: ****
      GROUP_ID: ***
      AUTO_DISC_RIPPER: 0
      APP_NICENESS: 19
    volumes:
      - "/volume1/docker.....:/config:rw"
      - "/volume1/storage:/storage:rw"
      - "/volume1/output:/output:rw"
    devices:
      - "/dev/sg5:/dev/sg5"

99-usb-cdrom.rules:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18a5", ATTRS{idProduct}=="0428", GROUP="cdrom", MODE="0666"

Optical drive is mounted as sg5.

• pulled the V_ID & P_ID with USB_Deview (see code above) and put'em into the rules file.
• copied the .rules file file to rules.d on my host system
• chmod 0666 /dev/sg5

container starts, VNC access works, I'm able to remux local isos but the optical drive doesn't work.
It is recognised by the container and makemkv.
If I insert a disc, it starts spinning in makemkv and after ~60 seconds I get several messages:

SCSI Error "NOTREADY: logical unit is in process of becoming ready - offset xxxxxx"
udf: node fe/efe failed

I've redone the whole procedure multiple times, including rebooting the system....

Any idea that could help me here?

Based on what I'm seeing, it seems as if there's some kind of hardware error spinning up the drive. If MakeMKV can see the drive and start using it, it has permission to access it.

Ok, it's a thing between my Synology and the drive then...
I'll google how to fix it, thank you!

Emilyst, I'm trying to help a friend get MakeMKV working on his Synology DS224+, and had a couple questions.

Is Docker installed with Synology's Container Manager?

Do I need to define the idVendor or idProduct when setting:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="", ATTRS{idProduct}=="", GROUP="cdrom", MODE="0666"