On 9/11/2026 at 11:07 PM, Djoss said:

Is the backup folder the only exception ? Do mkv files of a ripped disc have correct permissions ?

"User ID: 99" and "Group ID: 100" is correct, files have correct permissions but there'a a problem with Variable UMASK.

Change the UMASK value and nothing is changed with permission.

What's the best way to diagnose issues with an install?

Despite my best efforts I still can't get this one to work. I've tried literally everything and no dice.

ie. passing drives to the containers; changing PUID and PGID; literally everything I can find online.

8 hours ago, Dazzler said:

What's the best way to diagnose issues with an install?

Despite my best efforts I still can't get this one to work. I've tried literally everything and no dice.

ie. passing drives to the containers; changing PUID and PGID; literally everything I can find online.

what kind of issues by default it will try and pull the beta key, which sometimes works... you need a makemkv license...
https://forum.makemkv.com/forum/viewtopic.php?t=1053

Second, what kind of dvd/blueray disk drive, and how is it connected to Unraid...
*now all disk firmware is compatible with the needed functions to read and rip disks...
https://forum.makemkv.com/forum/viewforum.php?f=19

Third, what does Unraid see to pass the disk...
ls /dev/{cdrom,sr*,sg*}
As seen earlier in the forum:
https://forums.unraid.net/topic/182065-resetting-optical-devsr-devices-without-a-restart/#findComment-1496296
you will need to pass all /dev/sr# and /dev/srg#

Fourth, file permissions and Docker permissions...

chmod 777 and chown nobody:users

Waiting on changes; I've moved to Docker Compose... here is my working Docker Compose version...
I use this with a single Asus Blu-ray connected via acpi usb...

This is my working Docker Compose config... the Unraid default template; you need to add the device based on what your Unraid box sees as the disk drive... the default config works out of the box...

name: makemkv
services:
  makemkv:
    image: jlesage/makemkv:latest
    container_name: MakeMKV
    restart: unless-stopped
    # Debian cgroup v2 resource controls
    mem_reservation: 2g
    mem_limit: 6g
    memswap_limit: 8g
    #cpu_shares: 2048
    pids_limit: 2048
    shm_size: 2gb
    #privileged: true
    environment:
      - TZ=America/Chicago
      - MAKEMKV_KEY=BETA
      - AUTO_DISC_RIPPER=1
      - AUTO_DISC_RIPPER_EJECT=1
      - AUTO_DISC_RIPPER_PARALLEL_RIP=0
      - AUTO_DISC_RIPPER_BD_MODE=mkv
      - AUTO_DISC_RIPPER_DVD_MODE=mkv
      - AUTO_DISC_RIPPER_FORCE_UNIQUE_OUTPUT_DIR=0
      - AUTO_DISC_RIPPER_NO_GUI_PROGRESS=0
      - USER_ID=0
      - GROUP_ID=0
      - APP_NICENESS=0
      - DISPLAY_WIDTH=1920
      - DISPLAY_HEIGHT=1080
      - DARK_MODE=1
      - WEB_AUDIO=0
      - WEB_FILE_MANAGER=0
      - WEB_FILE_MANAGER_ALLOWED_PATHS=AUTO
      - WEB_FILE_MANAGER_DENIED_PATHS=None
      - WEB_NOTIFICATION=0
      - WEB_AUTHENTICATION=0
      - WEB_AUTHENTICATION_TOKEN_VALIDITY_TIME=24
      - WEB_AUTHENTICATION_USERNAME=
      - WEB_AUTHENTICATION_PASSWORD=
      - SECURE_CONNECTION=0
      - SECURE_CONNECTION_VNC_METHOD=SSL
      - SECURE_CONNECTION_CERTS_CHECK_INTERVAL=60
      - WEB_LISTENING_PORT=5800
      - VNC_LISTENING_PORT=5900
      - MAKEMKV_GUI=1
      - AUTO_DISC_RIPPER_MAKEMKV_PROFILE=
      - AUTO_DISC_RIPPER_INTERVAL=5
      - AUTO_DISC_RIPPER_MIN_TITLE_LENGTH=
    ports:
      - 7806:5800/tcp
      - 7906:5900/tcp
    volumes:
      - /mnt/users/This is the path to the makemkv needed docker data/storage:/storage:rw
      - /mnt/users/This is the path to the riped disk:/output:rw
      - /mnt/users/This is the path to the appdata config:/config:rw
    tmpfs:
      - /tmp:size=1g,mode=1777
    #security_opt:
    #  - apparmor=unconfined
    #  - seccomp=unconfined
    #cap_add:
    #  - SYS_ADMIN
    devices:
      - /dev/sr0:/dev/sr0
      - /dev/sg0:/dev/sg0
      - /dev/sg1:/dev/sg1
      - /dev/sg2:/dev/sg2
      - /dev/sg3:/dev/sg3
      - /dev/sg4:/dev/sg4
      - /dev/sg5:/dev/sg5
      - /dev/sg5:/dev/sg6
      - /dev/sg5:/dev/sg7
networks: {}

• You can add the above compose to a docker run to test...
  https://www.decomposerize.com/

  And pull the side data that I may or may not have in the above compose to add a manula unraid option... (data lost in this post as I've shared my template and config data before... including the extra option to add the disk drive
  
  I have moved away from Unraid and now run Debian due to other issues, so I wish you luck... all I can say is go back to post 1 and move forward; your issues may have been addressed already...

This is where it's stuck now.

After updating to the latest version v.26.09.2 (MakeMKV 2.0.0) it now crashes as soon as I open a disc. There's no particular error message in the logs so I'm not sure where to start troubleshooting.

Rolling back to v26.09.1 (MakeMKV 1.18.4) works as normal. Is anyone else experiencing this?

On 9/26/2026 at 12:13 AM, Excessiive said:

Rolling back to v26.09.1 (MakeMKV 1.18.4) works as normal. Is anyone else experiencing this?

@Djoss Confirmed. I just came here to report as well. The latest v26.09.2 crashes as soon as a disk is being loaded. No log entry, nothing. Just crash.

On 9/9/2026 at 8:46 AM, PicPoc said:

Hi !

UMASK=0000 doesn't work :

Extract from my-MakeMKV.xml :

<Config Name="Umask" Target="UMASK" Default="0000" Mode="" Description="Mask that controls how file permissions are set for newly created files. The value of the mask is in octal notation." Type="Variable" Display="advanced" Required="False" Mask="False">0000</Config>

ls ... :

drwxr-xr-x 1 nobody users 2026-09-09 08:34:10 backup

unmask=0000 : This means that it creates the folder with permission "drwxrwxrwx", right ?!?

Is it me or ???

Thanks ;)

I found the problem !

By default, the xml is set like this :

Storage "Access Mode:" Read Only

You have to modify to "Read/Write"

Of course, you have to edit XML with "Advanced View"

Please update your XML template original file to make Read/Write for output. ;)

.../jlesage-MakeMKV-latest.xml

OOps. No ! False way : nothing as changed

drwxr-xr-x 1 nobody users backup

Is ther anyway to modifiy this problem of "backup" folder permissions ?

Thanks ;)

while i'm not experiencing these issues with the latest and have used this same docker on other platforms. I am using an older generated appdata config settings file...



# MakeMKV settings file, written by MakeMKV v1.18.3 linux(x64-release)

Example of my settings.conf

#
# MakeMKV settings file, written by MakeMKV v1.18.3 linux(x64-release)
#

app_DataDir = "/config/data"
app_DestinationDir = "/output"
app_DestinationType = "2"
app_InterfaceLanguage = "eng"
app_Java = ""
app_Key = "my mkv key"
app_PreferredLanguage = "eng"
app_Proxy = ""
app_ShowDebug = "1"
app_ccextractor = "/opt/makemkv/bin/mmccextr"
bdplus_DumpAlways = "1"
sdf_Stop = ""
speed_ASUS_BC-12B1ST___b_3.00_211512151340_SIK9RH1LJ494 = ""

I can only recommend deleting the AppData folder as deleting the Docker from the Unraid webUI DOES NOT remove old configuration, which may be broken or problematic. DELETE YOUR OLD APPDATA FOLDERS!!!

Having a Unraid test system, this Docker is working correctly out of the box on a fresh Unraid... but I made the folder beforehand and set Docker safe permissions per Unraid tools, which sets 777 and nobody:users...

https://hub.docker.com/r/jlesage/makemkv/tags
jlesage/makemkv:v1.18.1

so I would recommend those having issues to use the older Docker tagged image...
then once its up and working. stop the Docker, edit it and bring it to the latest
jlesage/makemkv:latest as of writing:
jlesage/makemkv:v26.09.2

Edited Sunday at 10:23 PM2 days by bmartino1
spelling

Alright, I've got a new one. I recently did the update to latest about a week ago. Since I did that update, MakeMKV has entirely stopped being able to recognize BluRays for me, but it's still ripping DVDs just fine. Anyone else deal with that before? I'm not really seeing anything on either this thread or the MakeMKV reddit about it.

1 hour ago, Alhon said:

Alright, I've got a new one. I recently did the update to latest about a week ago. Since I did that update, MakeMKV has entirely stopped being able to recognize BluRays for me, but it's still ripping DVDs just fine. Anyone else deal with that before? I'm not really seeing anything on either this thread or the MakeMKV reddit about it.

sounds like your ptr data dind't download and or issues with decod file...

blueray pulls and makes a privatedata tar file




I would have you mkae sure the config folder has read write unraid docker safe permissions 777 and nobody:users

I would also have you double check your makmkv settings


But I can confirm the lattest image is working...

MakeMKV | ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮

MakeMKV | │ │

MakeMKV | │ Application: MakeMKV │

MakeMKV | │ Application Version: 2.0.0 │

MakeMKV | │ Docker Image Version: 26.09.2 │

MakeMKV | │ Docker Image Platform: linux/amd64 │

MakeMKV | │ │

23 hours ago, bmartino1 said:

sounds like your ptr data dind't download and or issues with decod file...

blueray pulls and makes a privatedata tar file




I would have you mkae sure the config folder has read write unraid docker safe permissions 777 and nobody:users

I would also have you double check your makmkv settings


But I can confirm the lattest image is working...

MakeMKV | ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮

MakeMKV | │ │

MakeMKV | │ Application: MakeMKV │

MakeMKV | │ Application Version: 2.0.0 │

MakeMKV | │ Docker Image Version: 26.09.2 │

MakeMKV | │ Docker Image Platform: linux/amd64 │

MakeMKV | │ │

Did some digging, and for some reason it did stop updating my _private-data.tar file. I read up that it's a safe file to delete since it gets bogged down with data for discs already ripped, so I cleared it out. MakeMKV regenerated it fine at 2KB, but it isn't populating or doing anything more with it. I've got all my permissions set up fine (I hadn't changed them in the first place), so not sure what's shut everything down here.

Do we know an IP that it's suppoed to be pulling this from, in case there's something in my firewall blocking the pull down? I can try to ping it out of my terminal, if only to eliminate a potential problem source. And it's unlikely, but a data center in the soviet bloc DID get blown up this past weekend.

2 hours ago, Alhon said:

Did some digging, and for some reason it did stop updating my _private-data.tar file. I read up that it's a safe file to delete since it gets bogged down with data for discs already ripped, so I cleared it out. MakeMKV regenerated it fine at 2KB, but it isn't populating or doing anything more with it. I've got all my permissions set up fine (I hadn't changed them in the first place), so not sure what's shut everything down here.

Do we know an IP that it's suppoed to be pulling this from, in case there's something in my firewall blocking the pull down? I can try to ping it out of my terminal, if only to eliminate a potential problem source. And it's unlikely, but a data center in the soviet bloc DID get blown up this past weekend.

I did at one time but it has changed. A lot of it, if any, is pulled from the website and their forum.... https://forum.makemkv.com/forum/ if any at all... similar with older variation of the DVD encryption key and the large number being a prime number university researcher prime number archive using a long number to get the dvd decode key example...

with the above options checked mkaemkv dumps and pulls a simlar decode data from disk (and per disk drive firmware) I've had good luck with LG and asus with makemkv not all disk drives work... Sorry, I don't know that data off hand any more if it is talking elsewhere at all...

there may be more info int in the code of the github porject:
https://github.com/jlesage/docker-makemkv