sparklyballs

Community Developer
 View Profile  See their activity

  • Posts

    3199

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by sparklyballs

  1. sparklyballs
    why would you need this then if plex is going to handle your library ? just send updates from your downloaders etc to plex instead
  2. sparklyballs
    i'd say there's something wrong with your host rather than this being anything related to our image
  3. sparklyballs
    @CHBMB ^^
  4. sparklyballs
    not that i'm aware of i don't use plex let alone tautulli but just going through the motions of adding it i can change the host port you don't want to ever change the container port as a rule anyways
  5. sparklyballs
    that's a host file system issue with (i believe not to be taken as gospel) fuse thinking the files are busy stop/start the array or stop the array and reboot and try again
  6. sparklyballs
    we don't recommend updating through the webui for instance you'd be missing a dependency that was added as part of the rebrand
  7. sparklyballs
    while unifi make great hardware their software sometimes falls short of the mark as @saarg alluded to we switched from using the repo as it was constantly changing the other thing with them is there seems to be a significant difference between a "stable release" and what is on their download page on at least 3 occasions they have pulled a stable release because it had issues
  8. sparklyballs
    @ICDeadPpl i'd suggest opening an issue here https://github.com/Jackett/Jackett and please for the sake of everyone's scrolling fingers use pastebin or similar service for a log of that size
  9. sparklyballs
    you need a postgres server before using this https://github.com/linuxserver/docker-tt-rss#setting-up-the-application
  10. sparklyballs
    this is a radarr issue rather than specifically docker
  11. sparklyballs
    we've rebuilt the image using last weeks mono baseimage and you should be able to pull latest without the need for any hotfix hopefully this should be resolved soon as upstream devs make their apps compatible with newer mono
  12. sparklyballs
    it appears the mono update has broken a bunch of downstream apps for this week we have reverted to last weeks baseimage build and rebuilt all our mono based apps using it try pulling an update
  13. sparklyballs
    issue raised with daapd dev for version 26 https://github.com/ejurgensen/forked-daapd/issues/502
  14. sparklyballs
    v26 crashes almost immediately in alpine and after about ten seconds of playing any music in itunes with a test rebase to ubuntu xenial i'm gonna raise an issue with forked-daapd dev
  15. sparklyballs
    volkion lidarr is the same as ours (using our baseimage in fact)
  16. sparklyballs
    the ball is in radarr dev's court to mitigate against mono latest version they are aware of it
  17. sparklyballs
    I'll take the vote of confidence but i just got the info from someone in a radarr git issue thread
  18. sparklyballs
    for radarr "press enter to exit" loop try exec'ing in to the container and running cd /opt/radarr && curl -o - http://download.sonarr.tv/hotfixes/regression-mono-5.10/NLog.dll.gz | gunzip -c > NLog.dll and then restarting the container
  19. sparklyballs
    both of the above questions would be better suited to asking lidarr dev team directly as they're both issues with the app itself rather than specifically our container you can either raise issues here https://github.com/lidarr/Lidarr or speak to them via their discord channel https://discord.gg/8Y7rDc9
  20. sparklyballs
    that's not ours (linuxserver's) resilio-sync that's limetech's
  21. sparklyballs
    there is no way to change to nightlies with our image in our experience nightlies often break more than they fix if you must use nightlies the Radar readme has a link to another image that uses nightlies should also add have no idea about whether you can migrate existing appdata to the nightlies docker and is certainly not something we support
  22. sparklyballs
    nothing to worry about "errors" from syncing that are safe to ignore
  23. sparklyballs
    chmod +x on those too and don't run the damn newperms script again lol
  24. sparklyballs
    have you run the newperms script at any time recently ? but to fix from the unraid terminal cd to your appdata folder for this container and run chmod +x ts3server
  25. sparklyballs
    this would be better off here https://lime-technology.com/forums/forum/47-docker-containers/