Djoss

Community Developer
  • Posts

    2356
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Djoss

  1. What "top" shows when run on unRAID itself (not inside the container) ? Looks like something else than the container is using all the CPU ?
  2. 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.
  3. 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 ?
  4. 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.
  5. No, this container doesn't support nvenc.
  6. 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.
  7. 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.
  8. 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".
  9. The problem seems to be related to the font used. Did you change it the the profile ? Can you try to edit the profile and see what is configured ? Not sure why it gives an error now, since nothing related to that changed from the last version...
  10. Looks like JDownloader is running now ?
  11. Are you connecting using an existing profile ?
  12. Could you provide the output of: docker exec JDownloader2 ps
  13. The template had incorrect default values for these settings. This is now fixed. If you prefer to set the credentials from JDownloader, just make sure to clear the incorrect default values from container's settings.
  14. Ok, the Docker image has been updated with this new version!
  15. Which issue exactly you are referring to ?
  16. How do you set credentials ? Via the JDownloader interface or via environment variables ?
  17. Did you try to remove and re-create the container ?
  18. This is expected. /storage is a different mount mapped to /mnt/user in unRAID. Other files and folders are from the Docker image itself.
  19. Humm this command should output something... Did you run "docker exec CloudBerryBackup mount" ?
  20. Yes sorry, I wanted to see the output of the command.
  21. The mount type for "/" is different in both cases. Since CloudBerry Backup seems to work by mount point, it is possible that it doesn't recognize it. Under XFS, can you try to run "docker exec CloudBerryBackup mount" ? From the app's point of view, it's not really important if it is running in a container or not. However, support might be quick to close your case by answering that running in a container is not officially supported.
  22. You should probably try to contact CloudBerry support about this. No need to indicate that you are using a Docker container. Just tell that the root folder "/" is missing from the Backup source.
  23. What about: ls -la /mnt/user/appdata/JDownloader2/ Did you try to remove and re-create the container ?