Djoss

Community Developer
  • Posts

    2356
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Djoss

  1. Does this directory have proper permissions to allow the container to write to it ?
  2. These apply only when the "Network Type" setting in the same page is set to "Bridge". From what I understand, this is not your case. So the "WEB Port fo rGUI (Bridge Network Type)" and "VNC Port for GUI (Bridge Network Type)" settings don't apply and are not used in your case.
  3. Even if it's the same folder on the host, it's different folders/mountpoints inside the container. This is why the move if in fact a copy+delete.
  4. AMC options are documented here: https://www.filebot.net/forums/viewtopic.php?t=215
  5. There is no variable that control that. However, you can add the following to the "Automated Media Center: Custom Options" setting: --def movieDB=TheMovieDB --def seriesDB=TheTVDB
  6. So Filebot is idle and doing nothing ?
  7. What was this entity ? By default the app is running under the correct user (nobody/users). My guess is that the files that didn't have the correct ownership were create by another app that was not running under this user ?
  8. The current beta key is expired. We need to wait for the MakeMKV author to publish a new one. See https://github.com/jlesage/docker-makemkv#expired-beta-key
  9. In container's setting, you need to add a new "Path". This path should be R/W and will be used to store the local backup. When you create the path, you map a path in unRAID to a path inside the container. Inside the container you can simply use something like "/localbackup".
  10. The enterprise version exists for a while, but I added the unRAID template recently. Good timing
  11. No. Are you able to confirm with your logs if failure started with version 23.10.1 (released on October 20) ? Also, can you confirm if the filesystem you use supports xattr ?
  12. Looks like xattr is no supported by your filesystem ? In container's settings, you may try to add "-no-xattr" to "Custom Options".
  13. Yes, a new image with HandBrake 1.7 is now available.
  14. Did you try to contact the CrashPlan support team ? Maybe there is an issue their side ?
  15. So if the file is changing location/directory, you need to make sure this is done under the same mount point inside the container. To better understand, maybe you can provide an example.
  16. The amount of memory needed directly depends on the amount of data you have to backup, something that probably increases with time. CrashPlan suggests to allocate about 1GB per TB of backup data.
  17. Yeah it seems to have an issue with the Docker Hub: images can't be pulled right now... This is what I have if I try to manually pull the image: docker pull jlesage/crashplan-pro Using default tag: latest Error response from daemon: Get "https://registry-1.docker.io/v2/": EOF
  18. Do you mean that the file is moved to a new location ?
  19. You should save videos under /output instead. By default, the mapping to /storage is read-only. Yes something needs to be incorrectly configured. Can you share the container's config ?
  20. Is it working when encoding with the same preset with the GUI ? Also, you may look at /mnt/user/appdata/HandBrake/log/hb/conversion.log to see if there is more details.
  21. This issue has been seen in the past and people reported that a reboot of the host fixed the problem.