Okay, so I did in fact make a transmissionvpn docker based on the rutorrent one.

I can make de repo public, but only if Binhex wants me to as I only modified his stuff. (Just let me know what you want Binhex)

Okay, so I did in fact make a transmissionvpn docker based on the rutorrent one.

I can make de repo public, but only if Binhex wants me to as I only modified his stuff. (Just let me know what you want Binhex)

Go for it, I have no issues with people using the code I've created as a base to create other docker images :-). You will need to tell a unraid forum moderator and they can then edit your account and give you developer status.

 

Sent from my SM-G900F using Tapatalk

 

 

Okay, for people reading this:

The dockerhub link is now public and it is:

https://hub.docker.com/r/activ/arch-transmissionvpn/

 

And for easy use in Unraid:

https://github.com/activ/docker-templates

 

Okay, for people reading this:

The dockerhub link is now public and it is:

https://hub.docker.com/r/activ/arch-transmissionvpn/

 

And for easy use in Unraid:

https://github.com/activ/docker-templates

 

nice work there, spotted a couple of tidy up tasks for you, other than that it looks pretty sound:-

 

1. delete the config folder as you aren't using pre-defined config files  for transmission - https://github.com/activ/arch-transmissionvpn/tree/master/config/nobody

2. delete aor.sh file, as i see your modifying the server list and then using pacman instead - https://github.com/activ/arch-transmissionvpn/blob/master/setup/root/aor.sh

 

i was toying with the idea of doing exactly what you did above in step 2. but chickened out as it does muddy things a little, as the base image is created from a snapshot in time, you are then switching this snapshot point to todays date, which is fine but could cause some conflicts with older packages, esp if some existing packages then get upgraded as pre-reqs for the app your installing, but it is def neater :-).

 

one last thing, i would recommend getting this all laid out in your own support thread, as you might be surprised by the number of people interested in this :-), oh and contact squid and he will get your app added to CA.

 

edit - check out my commit last night, i spotted a condition yesterday where a auth failure by your vpn provider causes openvpn to sigterm, in my case this was caused by a simple server issue at the vpn providers end, so i want to basically retry connection on failure, this is now baked into the intermediate image, and as your using this image in your from statement if you force a build you will pick this change up.

 

Thanks, did the housekeeping and updates the image to include your changes.

Should also be in CA soon.

 

I had to go for a newer repo as the fixed date one got me an old version of Transmission I didn't want and I didn't like the idea of grabbing an installer from some random place. So this seemed like the cleanest solution.

 

I've actually also been thinking about creating a more efficient vpn setup where one openvpn docker can serve multiple other dockers running things like Transmission and Sabnzbd, but I think that would probably end up being something that is not compatible with the Unraid UI.

I've actually also been thinking about creating a more efficient vpn setup where one openvpn docker can serve multiple other dockers running things like Transmission and Sabnzbd, but I think that would probably end up being something that is not compatible with the Unraid UI.

 

i too had that dream :-), a flexible openvpn container where you docker link in applications that you want to force down the tunnel, its possible but as you pointed out the unraid ui isnt really up to it, it would mean extensive use of the "extra parameters" section in advanced view, not to mention a bit of work to make the applications "aware" of this hook in, there would still need to be some modifications of things depending on the app, and at the end of the day what really do you want to run in the tunnel, its really only torrent clients and/or metadata for apps (covered by privoxy), so although technically it would be pretty cool, its not really a major problem, at least not in my opinion :-)

I have started to see a number of warning messages appear at the top of my Docker tab which seem to be related to the binhex dockers.  This may have started when I had a play with the Emby docker a couple of days ago.

 

What I see is:

Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/teamspeak.xml, line: 48 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/sonarr.xml, line: 67 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/sickrage.xml, line: 62 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/sickbeard.xml, line: 62 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/sabnzbd.xml, line: 61 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/plex.xml, line: 55 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/nzbget.xml, line: 56 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/moviegrabber.xml, line: 62 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/minidlna.xml, line: 51 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/madsonic.xml, line: 70 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/get-iplayer.xml, line: 62 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/delugevpn.xml, line: 111 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/deluge.xml, line: 71 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/couchpotato.xml, line: 63 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/sabnzbdvpn.xml, line: 107 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/jenkins.xml, line: 55 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/emby.xml, line: 56 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/plexpass.xml, line: 55 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/tvheadend.xml, line: 61 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214 Warning: DOMDocument::load(): EntityRef: expecting ';' in /boot/config/plugins/dockerMan/templates/binhex/rtorrentvpn.xml, line: 115 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 214
  	Application 	Author / Repo 	Version 	Port Mappings (App to Host) 	Volume Mappings (App to Host) 	Autostart 	Log

 

Now, I'm not using all of the dockers mentioned in the messages, so I presume that this is something fairly general (to do with your PayPal link?).

 

I'm running unRAID v6.1.9, if that's relevant.

Probably fixed now.  There was some template issues yeaterday.  You may however have to remove and readd the app via CA

 

Sent from my LG-D852 using Tapatalk

 

 

Probably fixed now.  There was some template issues yeaterday.  You may however have to remove and readd the app via CA

 

I removed, and re-added, the emby docker.  The dates/times of the xml files in templates/binhex have updated, but the problem is still present.  The reported lineno refers to the DonateLink element in every case.

Probably fixed now.  There was some template issues yeaterday.  You may however have to remove and readd the app via CA

 

I removed, and re-added, the emby docker.  The dates/times of the xml files in templates/binhex have updated, but the problem is still present.  The reported lineno refers to the DonateLink element in every case.

How are you adding it?  Just trying it now with no problems.  Make a note of the mappings / ports / etc, then remove the container (don't need to remove the image), then add it back again via CA (NOT using the previous apps section)

How are you adding it?  Just trying it now with no problems.  Make a note of the mappings / ports / etc, then remove the container (don't need to remove the image), then add it back again via CA (NOT using the previous apps section)

 

I have just followed that procedure on binhex-emby (twice, once with CA 2016.06.12, and then with CA 2016.06.13).  The problem still persists (and I note that it also affects the Apps tab).

 

Edit to add:

Okay, it seems that a reboot was required.  All is back to normal after this afternoon's powercut.

Thanks for the hard work.

 

#archlinux #respect

having trouble starting Madsonic:

 

HTTP ERROR: 503

 

Problem accessing /index.view. Reason:

 

    Service Unavailable

 

Has been working for a long time and earlier i had to redo the docker.img but since then this error has occurred, same config path etc as previous (same template my-binhex-madsonic)

 

I see a couple others report the same here https://hub.docker.com/r/binhex/arch-madsonic/

 

I recently installed tvheadend-unstable, and since then I have noticed an issue with my sickbeard docker gui crashing with the following error. I use google chrome on a mac and if I go in and clear the cookies, it resolves the problem for a time, but ultimately crashes again. No idea whats causing this.

 

400 Bad Request

 

Illegal cookie name ys-api/dvr/entry/grid_upcoming

 

Traceback (most recent call last):

  File "/usr/lib/sickbeard/cherrypy/_cprequest.py", line 625, in respond

    self.process_headers()

  File "/usr/lib/sickbeard/cherrypy/_cprequest.py", line 724, in process_headers

    raise cherrypy.HTTPError(400, msg)

HTTPError: (400, 'Illegal cookie name ys-api/dvr/entry/grid_upcoming')

Powered by CherryPy 3.2.0rc1

Are these docker images still being updated? I've just plugged my system back in after an 8 month hiatus from living with a slow ass connection and after checking, there aren't any updates available apparently?

Are these docker images still being updated? I've just plugged my system back in after an 8 month hiatus from living with a slow ass connection and after checking, there aren't any updates available apparently?

If you're on 6.1.x you have to hit advanced, then force updates.  Due to changes @ docker Hub, the update checks do not work on 6.1 anymore

The. Thanks!

Are binhex's docker containers still being updated?  I haven't seen an update to Plex (still sitting on version 0.9.16.6), Couch Potato, or sabnzbd in months.    Every time I check, Unraid says they're all up to date.

 

Just want to make sure I don't need to switch to linuxserver or one of the other maintainers.  Thanks!

Are binhex's docker containers still being updated?  I haven't seen an update to Plex (still sitting on version 0.9.16.6), Couch Potato, or sabnzbd in months.    Every time I check, Unraid says they're all up to date.

 

Just want to make sure I don't need to switch to linuxserver or one of the other maintainers.  Thanks!

They are updated. Unraid's docker update notification is broken. If you switch to advanced view, and force update, you will get the updated version.

Are binhex's docker containers still being updated?  I haven't seen an update to Plex (still sitting on version 0.9.16.6), Couch Potato, or sabnzbd in months.    Every time I check, Unraid says they're all up to date.

 

Just want to make sure I don't need to switch to linuxserver or one of the other maintainers.  Thanks!

They are updated. Unraid's docker update notification is broken. If you switch to advanced view, and force update, you will get the updated version.

 

Thanks!  Doing that now.  I didn't even know there was an advanced view on that screen.

 

Weird that it's broken now, up until a few months ago the notifier worked fine.  Thanks again!

Adding snapshots of my delugevpn docker setup for a fellow user who needs some help. This post is for reference only to share my setup pictures and I am not asking for help!

 

ok, just so you know the LAN_NETWORK value you have is incorrect, it should be 10.10.1.0/24

binhex - In have set my ip addresses to start at 10.10.1.1. I would think that should be the LAN network value. isnt it?

 

ok, just so you know the LAN_NETWORK value you have is incorrect, it should be 10.10.1.0/24

binhex - In have set my ip addresses to start at 10.10.1.1. I would think that should be the LAN network value. isnt it?

 

ok, just so you know the LAN_NETWORK value you have is incorrect, it should be 10.10.1.0/24

http://www.subnet-calculator.com/cidr.php

binhex - In have set my ip addresses to start at 10.10.1.1. I would think that should be the LAN network value. isnt it?

 

ok, just so you know the LAN_NETWORK value you have is incorrect, it should be 10.10.1.0/24

http://www.subnet-calculator.com/cidr.php

 

Cool link.... I'm going to have a play around with that.  Thanks jonathan