Jump to content

activ

Community Developer
  • Posts

    126
  • Joined

  • Last visited

Posts posted by activ

  1. Are you installing on Unraid? Using my repo or another way?

     

    I guess you need to correct some stuff if you are running the command manually some stugg I notice in the command you pasted:

     

    Where it says: VPN_PROV="pia|airvpn|custom" you will need to choose one.

    WHITELIST="192.168.*.*" Should be changed to reflect your setup (WHITELIST="10.*.*.*")

    VPN_USER="vpn username" -e VPN_PASS="vpn password" need to be set

     

    I specifically think the pipe sign in VPN_PROV is causing your issue.

     

     

    • Upvote 1
  2. Update februari 2018: I no longer have the possibility to keep supporting this docker. If anyone wants to take over please feel free, grab my stuff from GitHub and make your own. I will leave the current state online, because I know people are using it.

     

    Overview: Support for Docker image arch-flexget in the activ repo.

     

    Application: Flexget - http://flexget.com

    Docker Hub: https://hub.docker.com/r/activ/arch-flexget

    GitHub: https://github.com/activ/arch-flexget

     

    Credit: I am using the base image made by Binhex, so most of the work was done by him.

    • Upvote 1
  3. bae47ae6eb1d47e920e03559d003c701.jpg

     

    I think I can answer my own question.

     

    Sent from my XT1563 using Tapatalk

     

    Hey Binhex: Is this something that's in your base image?

    I was thinking I'd build in the option to use a proxy in some other images, but if it's in your base I won't need to.

  4. Yes, that's expected. It's caused by now using git for the installation. My first version used git and didn't have this error, but using git in docker is actually not good practice (as noted by Binhex earlier).

     

    It's safe to ignore the message as it only prevents updates and doesn't impact anything else.

  5. I've now also done the switch from git to AUR,the update has been pushed to the docker repo.

     

    cool, one other thing you might want to consider is switching from building images locally to getting dockerhub to do the building, this has the advantage that you keep your build env off your environment, as well as people then being able to see the output of the build on dockerhub, not to mention support for tags too.

     

    so you can hook github and dockerhub together, and you then set it to auto trigger a build on any github commits or you can set dockerhub to manual trigger, i would advise the second option as this then gives you control to add in tags in dockerhub. tags are important and allows the users to roll back incase of either a bad build or an issue with the app, i basically tag all my releases with <aur release>-XX where XX is a numeric indicating my build count for that version, e.g. for lazylibrarian the tag for first build would be 736.d66f7e9-1-01, this is a funny one as its a github build number so its a bit more cryptic, but you get the idea :-).

     

    just to be clear when under heavy dev i would advise building locally until you are confident enough to push it to github and build using dockerhub, building locally is still faster than building on dockerhub.

     

    Sounds cool, I'll look into that.

  6. Have you tested deluge native connections? I'm getting an error

    Deluge: Connect FAILED
    [Errno 111] Connection refusedCheck Deluge HOST and PORT settings

    using the same settings that work successfully in sonarr and couchpotato.

     

    Hey, I'm not sure what you mean. Are you saying you are trying to have LazyLibrarian connect to the deluge in your other docker?

    No, I have not tested that. Don't really see why it would be an issue though.

     

    If the deluge is the one with vpn in it, maybe the iptables firewall is the one blocking things (there are several ip ranges involved).

     

    If you can give me a better picture of what you are trying to do I'll try and give you some troubleshooting tips.

  7. You mean you would set a variable selecting Transmission or Rutorrent etc?

    I'm not sure how that would work, the way I see it Dockers need to be as light weight as they can. Installing three pieces of software and then using only one isn't really light weight.

    Also, what would the advantage be? The way it is now you can run one of them or all of them at the same time as you want.

     

    A big wish for me is to have the Openvpn and torrent dockers seperated so you don't need to run the vpn several times, but I highly doubt I'll be able to do that and not break compatibility with the Unraid UI.

×
×
  • Create New...