Djoss

Thanks, I will provide my though in the thread you mentioned.

Yes I'm working on this. A new docker image should be available today.

Are you aware of the reasoning behind this change in 6.10? Why don't we continue let the maintainer chooses if its templates should be automatically updated or not? I find this update mechanism very useful to provide fixes, enhancements and additions to the template. Personally, I think I had only 1 reported issue related to the automatic template update. So I don't think that stopping template updates would reduce the number of support requests. This will probably increase it!

Inside the container, you should find your data under "/storage". So "/mnt/user/Lagring" in unRAID is mapped to "/storage" in the container.

Thanks for reporting, l will check this.

Did you check ownership/permissions on the .sparsebundle folder ? Maybe the problem is that the container doesn't have the permission to read it.

With encrypted connection, are you using a valid certificate ? If not, this is a known behaviour on iOS where a secure WebSocket connection won't be done is certificate can't be successfully validated. Not sure to I understand the problem. Don't forget that your are accessing a desktop application, not a mobile one. So the web interface used to access the desktop application is mobile friendly, but not the application itself.

Can you try to remove the comma from your AMC_CUSTOM_OPTIONS, like this: --def skipExtract=n --lang es

Can you get the container's log ? Are your other containers responding to docker commands ?

Update the container again, this should be fixed.

I don't see any issue on my side and I have about 30 tabs opened all the time. Are you using default container settings ? One thing you can do when the issue occurs is to login to the container (docker exec -ti Firefox sh) and run the "top" command. This will show which processes are using the cores.

Both will do the same thing. If you prefer to re-use the storage setting, just make sure to change its access mode to read/write. By default it's read-only.

You need to make sure that you use a single mount point. So I would add a new "Path", where you map /mnt/user to /workdir in the container. Then set: "Automated Media Center: Input Directory" --> /workdir/Downloads/Drop "Automated Media Center: Movie Format" --> /workdir/media/Movies/... "Automated Media Center: TV Series Format" --> /workdir/media/Shows/...

Can you share the full config of the container, by providing the output of "docker inspect FileBot" ? The problem may come from the value of one of the environment variable.

Try the latest Docker image. Problem should be solved.

This should be fixed with the latest Docker image version.

You can reset your password using the CrashPlan website (https://www.crashplan.com).

No impact, since Log4j is a Java library and Avidemux is not Java program.

Do you hava another GPU ? I'm not sure why you have card1/renderD129 instead of card0/renderD128. But anyway, these are just informational messages. Did you check if HandBrake is actually able to use QSV ?

You mean that the automatic video converted failed to encode a file ? Conversion log is located at /mnt/user/appdata/HandBrake/log/hb/conversion.log Note that it will not re-encode the same video again if it failed once. Try removing the source from the watch folder and re-add it. You can also remove /mnt/user/appdata/HandBrake/failed_conversions and restart the container

Running as root is not a good practice. There is no need to give too much privileges to the container. When exactly are you seeing these messages? Are they preventing FileBot to run? Can you provide the full container log ?

The new image is now available.

Yes the latest Docker image already integrates version 3.2.x. However, another version of CloudBerry Backup appeared since this. I will update the Docker image.

Code42 released a new version of CrashPlan yesterday, which fixes at least the log4j vulnerability. A new Docker image integrating this version will be released soon.

By default /storage is read-only. You normally have to write encoded files to /output in the container.