Djoss

Looks like the variables are not set properly. Did you create the container using the Community Apps plugin ? If not, how you did ?

Not sure what you mean by the "docker uninstalls itself". However, to add a device, you need to edit container settings, click "Add another Path, Port, Variable, Label or Device" and then select "Device" for the "Config Type". Also, make sure the device you add (e.g. /dev/sr0) really exists. For the log, please provide the complete log by running "docker logs MakeMKV".

Yes it should work. Are you using default template settings ? Are you using the UI or the automatic disc ripper ?

This directory with weird name is causing the problem: root@Tower:~# ls -la /mnt/cache/appdata/FileBot drwx------ 1 nobody users 28 Aug 9 2018 \n/ Removing it should fix your issue. I will make an update to better handle this scenario in the future.

👍

Can you provide the output of: ls -la /mnt/cache/appdata/FileBot And: echo START && find /mnt/cache/appdata/FileBot -maxdepth 1 -type d && echo END

Have you selected a QSV encoder in your preset ?

By default the container has only read access to your data. When you want to restore, you need to change that. Edit the container's settings, toggle the "Advanced View" (upper right corner), then edit the "Storage" setting and change the "Access Mode" to "Read/Write".

You can use the "Tips and Tweaks" unRAID plugin to increase the number of watches. The plugin shows the current number, along with the number used. There is no recommended values, since it depends directly on the number of files you backed. Using the plugin, try to increase the "Max User Watches" and then see how it goes.

The way to go for captcha is to enable MyJDownloader and use the MyJDownloader browser extension.

With default container settings, dupeGuru works with data under /mnt/user. To my knowledge this is safe and you cannot screw up things.

Thanks for reporting, I'm fixing this.

Please try the new image.

Thanks for reporting, I'm fixing this!

You mean the "dockerd" process ?

Ok great, thanks for the update!

What "top" shows when run on unRAID itself (not inside the container) ? Looks like something else than the container is using all the CPU ?

You were probably running v1.22.1 when you did your successful rip on 2022.10.13. So you are saying that you tried this same version and still had the issue ? I've seen some cases were the drive started to work again after a reboot, so maybe something to try.

The ":latest" tag is the default one when none is used. I've been able to update successfully recently these images. So maybe you should report your issue to the Community App plugin thread ?

Yes, I'm working on this!

Yes, this seem right. If the wrong preset is used during a conversion, look at /mnt/user/appdata/HandBrake/log/hb/conversion.log. You should be able to see what is the correct name to use for your preset.

No, this container doesn't support nvenc.

Are you using h265 encoder? There is currently a known issue that cause QSV error with HandBrake with some CPUs. Next version should fix that. You can see https://github.com/jlesage/docker-handbrake/issues/185 for workaround.

First make sure you custom preset works well when using the UI. Then you can set in preset to use in container's settings. If the wrong preset is used during a conversion, look at /mnt/user/appdata/HandBrake/log/hb/conversion.log. You should be able to see what is the correct name to use for your preset.

The startup of the container can take some time, especially the step "55-jdownloader2.sh: executing..." if you have a lot of stuff under "/output".