Leaderboard

Popular Content

Showing content with the highest reputation on 03/03/18 in all areas

  1. 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
    6 points
  2. Application Name: QDirStat -- Graphical view of directories, find files taking up the most space. Real MovieOS stuff! Application Site: https://github.com/shundhammer/qdirstat Docker Hub: https://hub.docker.com/r/mjdumont1/qdirstat Template-Repository: https://github.com/Jcloud67/Docker-Templates UI is through RDPclient, youTowerName:33389 Template defaults /mnt/user/ on host, as the container location /files/. Application Name: Storj.io daemon What is Storj? https://www.storj.io/ Application Site: https://github.co
    1 point
  3. A container on br0 can't communicate with one that has a dedicated ip. Limitation of docker networking. As for the SSH key add another path to the container /mnt/cache/appdata/home-assistant/ssh/id_rsa and map it to /.ssh/id_rsa
    1 point
  4. 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
    1 point
  5. Our images (linuxserver.io) are no different to any other image on docker hub, the only special thing about Unraid is that we produce an XML template to integrate it into the webui. You could in theory do so for any image on docker hub. Sent from my LG-H815 using Tapatalk
    1 point
  6. They are basically the same, one has vertical ports, the other horizontal, depending on your case one might be better, if not go with the cheapest.
    1 point
  7. The H200E has 2 external ports, there is the H200, same as H310, both have 2 internal miniSAS ports, only difference is the orientation.
    1 point
  8. (Relatively) Minor Issue, but an annoyance for those with multiple servers Starting with RC1, the local terminal (and any SSH terminals) do not show the name of the server any more (none) login: root@(none):~#
    1 point
  9. Copy/paste , I have that reply saved as I use it every week. SAS2008 are similar to SASLP/SAS2LP, they use the same power, SAS2308 runs a little hotter than SAS2008 due to higher clock speed, never had a SAS3008.
    1 point
  10. Yes. Any LSI with a SAS2008/2308/3008 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed.
    1 point
  11. 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
    1 point
  12. Yes, but note that controller is no longer recommended for v6 since it can drop disks for some users, still works for others without issues though.
    1 point
  13. the ball is in radarr dev's court to mitigate against mono latest version they are aware of it
    1 point
  14. Answering my own question: docker exec -it radarr /bin/bash Now all working again. And for future updates, I'll just follow the rule not to update unless something is broken.
    1 point
  15. Speaking of hyper visor, make sure you have it off.
    1 point
  16. Off original topic, but you can always try it for a month and see if it's something you like. The data is stored in standard Linux file-systems, so your data is never locked away in some DRM-locked-space. Sure the Distro isn't free, but considering the product: A stable distro. User setup/config has been done for you, and what setup/config to do has been wrapped into templates and a web interface. Then given the fact Lime-Technology has given the user a strong storage/data management, Application server, and KVM (hyper-visor). It's a one time fee, and price scales linear. Data is
    1 point
  17. People can already get to the support thread for any docker they are running from that docker's icon without even knowing the author.
    1 point
  18. No way would we be able to monitor that if everyone posted a new issue. Half the problem is people don't search, if everyone starts posting a new issue that would cause chaos for us people that have to support it. The whole point of a support thread is to keep issues with a particular container limited to one thread. I'm not joking when I say that if people can post a new issue rather than posting in an existing support thread, then I'll quit with support, I don't have time for that. I'm not averse to author specific subforums at all, but only on the basis that the on
    1 point
  19. Please guys. The rating of the PSU is not the determining factor in picking the size of the UPS, it is the power draw of the system. The fact that the PSU could deliver 1000W should not really be a consideration is picking the size of the UPS!
    1 point
  20. Im not sure, but i think thats wrong! Tunnel means it cant reach the port. Thats for sure. But it has nothing to do with network type bridge or host. Its because your standard config is "wrong". I changed it this way: After i just c hanged this. And port forwarded port 4000 - 4003 to the unraid machine, all is working without tunnel. No need to change network type, but i guess, you could change it if you want it. Just btw u also have a typo in the descriton from the docker template, there u say port forward port 400- 4003
    1 point
  21. The Docker reports tunneling due to a choice I made making template, If you want to remove that tunnel, in the template settings change "Network Type" from, "Bridge" to "Host" and then remove "Storj network ports" (which is a port forward from host to container, the source of your tunnel). I'm running it on the host port, I did notice the reported Delta went down; perhaps I made a bad setup choice. My logic at the time of setup, was that containers should be fully contained, also thought it would make potential port conflicts easier to change/explain on forums. Sorry nuhll I
    1 point
  22. Glad to hear about HTTPS support coming. Some other suggestions: - Have a default root password vs just blank. - Force password to be changed on first login. - ssh key support in the web interface.. more advanced users can do this today. - Run docker as its own user - Run KVM as its own user - Create a separate user account for the web interface that isn't root so you are not passing root creds over the network (although ssl sorta addresses this) Even with that you should never stick an unraid box on a DMZ port. It's use case is i
    1 point
  23. A easier method of discovering the right card to passthrough is running: #!/bin/bash for ETH in $(find /sys/devices/ -type d -iname "eth[0-9]"); do port=$(basename $ETH); export $(cat $ETH/device/uevent); link_status=$(cat $ETH/operstate); desc=$(lspci -d $PCI_ID| cut -d ':' -f3) pci_bus=$(echo $PCI_SLOT_NAME|sed -e 's#0000:##') echo -e "Found NIC: $port\n Name: $desc\n PCI id: $PCI_ID\n PCI bus: $pci_bus\n Status: $link_status\n" done
    1 point