Duplicate DVD names causes errors about docker-makemkv

[jlesage]

For your first issue, I tried to replicate and I could not. mkv files are always put in the correct folder. Are you using the latest version of the image? Maybe you could provide the container log showing the issue?

For you second point, I agree that it's a situation that could be fixed. I will check what would be the best way to achieve this.

[tb-lund]

Thank you for the reply. That is indeed very strange. I have been using the "latest" version but today also deleted it and forced the v1.9.3. Here is my starting parameters:

docker run -d \ --restart=unless-stopped \ --name=makemkv \ -p 5800:5800 \ -v /appdata/makemkv:/config:rw \ -v /appdata:/storage:ro \ -v /mnt/pve/NFS-media/Videos/Import/raw:/output:rw \ -e AUTO_DISC_RIPPER=1 \ -e AUTO_DISC_RIPPER_EJECT=1 \ -e AUTO_DISC_RIPPER_MIN_TITLE_LENGTH=360 \ -e UMASK=000 \ -e KEEP_APP_RUNNING=1 \ --device /dev/sr0 \ --device /dev/sg0 \ jlesage/makemkv:v1.9.3

I would be very happy to supply a log file, but the fact is that it does not generate any log file in the "appdata/makemkv/log" directory only the nginx log. Should I be looking elsewhere? The troubleshooting I have done is to run two disks from the same series. In this case my old "The West Wing" box.
The first disk generated the directory "THE_WEST_WING" and the files "title00.mkv", "title01.mkv", "title02.mkv", "title03.mkv".

When I insert the the second disk it generates a second directory "THE_WEST_WING-BpCbMi" then spins the disk for 30 seconds and ejects it without saving any files. Then I rename the .mkv files without renaming the directory e.g., title00.mkv to S1E1.mkv and insert the second disk again. Then it generates a third directory "THE_WEST_WING-pPOBFH" and runs the disk through but saves the "title00.mkv" in the original "THE_WEST_WING" directory.

Have I caused this through changes in the docker command?

[jlesage]

You can get the container log by executing the command docker logs [container name].

You should see messages showing the auto disc ripper working.

[tb-lund]

Thank you! Now I see the log.

Strangely enough it says "chown: /output/THE_WEST_WING-CHOpcD: Operation not permitted"
The output folder has men set to "777" and the docker container is run as root to avoid any such issues.

[jlesage]

Which type of filesystem/mount /raw is on the host?

[tb-lund]

This is a NFS mount from a NAS.

I have re-run it now with specifying the user through:

-e USER_ID=0
-e GROUP_ID=0 \

and skipped the:
-e UMASK=000 \

So far, it is actually working! Should have been the same user, i.e., root, but at least it is working.

[tb-lund]

For those who do run into the same issue. The problem is something called a "root_squash" which is default of NFS shares e.g., on the ReadyNas which I'm using. This disables the root function on the share and thus results in the "Operation not permitted" error. Fortunately, the solution is easy. Add "no_root_squash" in the parentheses section i.e.,
(insecure,insecure_locks,rw,no_root_squash,async)
to the share in /etc/exports of the NAS and reboot the NAS. then everything works as expected.

[jlesage]

Note that you should not have to run MakeMKV as root. So the next image update will have a fix that will allow you to run as non-root while still having the ability to set UMASK to 000.

The next update will also cover your first point.