Djoss

Did you map the mount to the container be adding a new "Path" in container settings ?

We need the full log from the beginning. If you can't scroll up, you can get the log from the terminal by executing the command "docker logs MakeMKV".

Can you share the container log ?

As a workaround/fallback method, you can copy-paste the shown URL and perform the login externally in your browser instead.

It was maybe the situation years ago, but it's no longer the case. Note that speed has always been an issue/limitation/trade-off. But if you are seeing difference between two versions of CrashPlan, it's worth checking if it's a bug.

The disc should be processed once. Maybe there are 2 versions of the movie on the disc ?

Did you report the issue to CrashPlan support team? Note that jlesage/crashplan-pro:v24.08.1 integrates CrashPlan version 11.4.0.

How did you configure the "Path" you added to the template / container settings ?

Can you check the output of "docker inspect MakeMKV" to confirm that the variable is properly set ? Do you see any related message when ripping a disc ? While ripping a disc, could your share the output of "ps" inside the container ?

I'm not sure I understand the question. What do you mean by ffmpeg support ? Video Duplicate Finder already use ffmpeg. Hardware decoding should work, see https://github.com/jlesage/docker-video-duplicate-finder/issues/7

New container mage now available

Seems to be this known issue: https://forum.makemkv.com/forum/viewtopic.php?f=3&t=35897

I just realized from log you provided that it's port 5900 that is conflicting. If I understood your setup correctly, you are not using the default bridge network, so you probably need to change the "VNC Listening Port (Non-Bridge Network Type)" setting (it can be set to -1 if not needed).

I don't have enough details to explain the reason... did you find another container that could use the same port ?

This should already work. What is the problem exactly ?

Looks like something else on your system is using the same port. Are you using the default container settings ?

This is the dark theme used: https://draculatheme.com/jdownloader2

Then check extensions installed/activated in Safari. One of them is probably causing the issue.

This is usually caused by a browser plugin/extension.

The crash should never fixed with the latest Docker image.

Great test, thank you for that. Can you report the issue on the MakeMKV forum ?

Maybe also check on the MakeMKV forum to see if there are any similar reports.

So looks like the issue might be with MakeMKV itself. Note that FFmpeg should not have any impact if audio is not transcoded.

Can you try jlesage/makemkv:ffmpeg4 (MakeMKV 1.17.9 + FFmpeg 4) ?

Do you see an increase in CPU usage (or do you see a high CPU usage while MakeMKV read the file) ? Do you reproduce the issue with all kind of images ? I tried on my side with a standard DVD image and I didn't see a problem.