Djoss

This might be caused by an issue on the host. Did you try to reboot the server ?

You want to install the docker container without internet ?

It's back now :)

Is this on a new install ? Or the container already worked in the past ?

This will be restored with the next version of the container image.

Since you have more than one container under the same non-bridge network, you need to configure different ports for each container. You can use the "Web Listening Port (Non-Bridge Network Type)" and VNC Listening Port (Non-Bridge Network Type) settings (in container configuration).

This is now fixed.

How you did your setup and what was the failure exactly ?

The container's log also shows the information, but you are better to use "docker logs MakeMKV", because the one shown from the web UI is truncated.

Thank you, I fixed the template!

Once the drive is plugged, just start/restart the container and look at its log: it will show which Linux devices need to be exposed to the container.

Looks like a folder permission issue. What are permissions the "media/serier" folder ?

Thank you! I will update the image.

Thank you for confirming that the new FFmpeg version fixes the problem. I will release a new image with the fix, so no need to keep using jlesage/makemkv:ffmpeg7.

Can you try the image jlesage/makemkv:ffmpeg7 to see if you still get the error ?

Access is ok for me now. Note that you don't need to enter the key yourself, the container takes care of that.

This container integrates the free/opensource version. The donation edition is a different software, for which the source code is not available and the binary cannot be distributed.

I found the source of the problem. This will be fixed with next version of the image.

Ok I was also able to reproduce my side. Since this is a behaviour of FreeFileSync itself, you should also ask on its forum: https://freefilesync.org/forum/ I can also check its source code to see if this is something than can be easily deactivated.

I don't see this problem on my side. Nothing is done automatically when the container starts. Could you share a screenshot of the UI showing the problem ? Is it really the main FreeFileSync instance that is doing the comparison and not one of the scheduled job ?

What do you mean by "automatic compare" ?

Note that there is no need to pass all these devices to the container. In your case, according to a previous screenshot, only /dev/sr0 and /dev/sg2 are needed (the ones associated your drive). You said that the drive was reading the discs under Windows. I assume you also used MakeMKV ? Could you share the output of "docker logs MakeMKV" ?

Can you provide more details about the failure ? Maybe the full container log ("docker logs dupeGuru")?

Review the full container log (docker logs MakeMKV) and make sure everything is fine for the detected drive. Also, I would recommend that you temporarily switch MakeMKV to English so that we can have a better understanding of the log it provides.

Do you get this problem for any discs ?