[ARCHIVE] binhex docker repository

[dikkiedirk]

I use the Community Applications plugin and I meant the Add button for your plugin there.

 

After clicking add I get to the Add container screen and leave everything alone. Just click create. Is that correct?

 

 

 

[dikkiedirk]

Oh boy, I didn't see you last reply as I was away for a moment and didn't refresh the screen.

[JustinChase]

if your still getting an issue, which im assuming you will, then please post the contents of your .ovpn file (located in /config/openvpn/) and the contents of the supervisord.log file (located in /config).

 

openvpn.opvn...

 

client
dev tun
proto udp
remote us-east.privateinternetaccess.com 1194
ping 300
ping-restart 600
ping 600
ping-restart 1200
resolv-retry infinite
nobind
persist-key
ca ca.crt
tls-client
remote-cert-tls server
auth-user-pass credentials.conf
comp-lzo
verb 1
reneg-sec 0
crl-verify crl.pem

 

supervisord.log...

 

2015-06-22 08:08:59,830 CRIT Set uid to user 0
2015-06-22 08:08:59,840 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2015-06-22 08:08:59,951 INFO supervisord started with pid 1
2015-06-22 08:09:00,953 INFO spawned: 'deluge' with pid 8
2015-06-22 08:09:00,953 INFO spawned: 'setip' with pid 9
2015-06-22 08:09:00,954 INFO spawned: 'start' with pid 10
2015-06-22 08:09:00,955 INFO spawned: 'webui' with pid 11
2015-06-22 08:09:00,956 INFO spawned: 'privoxy' with pid 12
2015-06-22 08:09:00,956 INFO spawned: 'setport' with pid 13
2015-06-22 08:09:00,961 DEBG 'deluge' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2015-06-22 08:09:00,961 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2015-06-22 08:09:00,961 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2015-06-22 08:09:00,961 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2015-06-22 08:09:00,961 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2015-06-22 08:09:00,962 DEBG 'privoxy' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2015-06-22 08:09:01,583 DEBG 'start' stdout output:
[info] VPN is enabled, beginning configuration of OpenVPN

2015-06-22 08:09:02,585 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-06-22 08:09:02,585 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-06-22 08:09:02,726 DEBG 'start' stdout output:
[info] VPN provider defined as pia

2015-06-22 08:09:03,128 DEBG 'start' stdout output:
[info] VPN provider remote and port defined as us-east.privateinternetaccess.com 1194

2015-06-22 08:09:04,035 DEBG 'start' stdout output:
[info] ip routing table

2015-06-22 08:09:04,036 DEBG 'start' stdout output:
default via 172.17.42.1 dev eth0 

2015-06-22 08:09:04,036 DEBG 'start' stdout output:
172.17.0.0/16 dev eth0  proto kernel  scope link  src 172.17.0.6 
--------------------

2015-06-22 08:09:06,113 DEBG 'start' stdout output:
[info] iptables

2015-06-22 08:09:06,114 DEBG 'start' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1194 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1194 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2015-06-22 08:09:06,114 DEBG 'start' stdout output:
--------------------

2015-06-22 08:09:06,114 DEBG 'start' stdout output:
[info] nameservers

2015-06-22 08:09:06,115 DEBG 'start' stdout output:
nameserver 8.8.8.8
nameserver 8.8.4.4

2015-06-22 08:09:06,115 DEBG 'start' stdout output:
--------------------
[info] Starting OpenVPN...

2015-06-22 08:09:07,403 DEBG 'start' stdout output:
Mon Jun 22 08:09:07 2015 OpenVPN 2.3.6 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec  2 2014
Mon Jun 22 08:09:07 2015 library versions: OpenSSL 1.0.2a 19 Mar 2015, LZO 2.09
Mon Jun 22 08:09:07 2015 WARNING: file 'credentials.conf' is group or others accessible

2015-06-22 08:09:08,163 DEBG 'start' stdout output:
Mon Jun 22 08:09:08 2015 UDPv4 link local: [undef]
Mon Jun 22 08:09:08 2015 UDPv4 link remote: [AF_INET]107.191.32.197:1194

2015-06-22 08:09:08,796 DEBG 'start' stdout output:
Mon Jun 22 08:09:08 2015 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

2015-06-22 08:09:16,160 DEBG 'start' stdout output:
Mon Jun 22 08:09:16 2015 [Private Internet Access] Peer Connection Initiated with [AF_INET]107.191.32.197:1194

2015-06-22 08:09:19,278 DEBG 'start' stdout output:
Mon Jun 22 08:09:19 2015 AUTH: Received control message: AUTH_FAILED

2015-06-22 08:09:19,278 DEBG 'start' stdout output:
Mon Jun 22 08:09:19 2015 SIGTERM[soft,auth-failure] received, process exiting

2015-06-22 08:09:19,279 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 46929994208680 for <Subprocess at 46929991958040 with name start in state RUNNING> (stdout)>
2015-06-22 08:09:19,279 DEBG fd 19 closed, stopped monitoring <POutputDispatcher at 46929994209112 for <Subprocess at 46929991958040 with name start in state RUNNING> (stderr)>
2015-06-22 08:09:19,279 INFO exited: start (exit status 0; expected)
2015-06-22 08:09:19,279 DEBG received SIGCLD indicating a child quit

 

Now that I know what logging to look at; it looks like authorization my be filing.  I'm 95% sure the user/pass is correct; I just updated them, and can login to the PIA site with them just fine, but I'll investigate more on my end also.

 

If there are any other ideas/issues, I really appreciate the help/feedback.

 

Thanks again.

[scytherbladez]

hi scytherbladez, i have switched the docker over to the standard par2 package, please keep in mind that the "clowns" you refer to is the only guy coding the multithreaded par2 library, this is not an off the wall random link, this is/was the only supported high performance par2 library currently available, so any reference to this in other dockers/plugins will have the same issue.

 

Thanks for the reply. I'm just a bit frustrated since I updated the sab docker I'm questioning whether it's "safe" or even worth "risking" updating dockers now... especially since I couldn't find a way to rollback the update. Learnt a bit about docker, but ultimately achieved nothing.

[JustinChase]

 

Now that I know what logging to look at; it looks like authorization my be filing.  I'm 95% sure the user/pass is correct; I just updated them, and can login to the PIA site with them just fine, but I'll investigate more on my end also.

 

If there are any other ideas/issues, I really appreciate the help/feedback.

 

Thanks again.

 

verified my login/pass is correct.  changed to their midwest server; that worked fine.  changed back to east, failed.  changed to midwest, worked.  changed to california, failed.  changed to new york, worked.

 

weird, but means it's likely not a docker problem, but a pia problem.

 

will work with them later today to resolve.

 

thanks again.

[johnc]

I am having an issue with the permissions of files created by the dockers.  I'm not sure if it's specific to the binhex dockers or just unRaid dockers in general.  But I'm specifically seeing it in the bixhex sabnzbd and sickrage dockers so I'm starting here.

 

What I'm seeing is that all files/directories are being created with an owner of "nobody" and a group of "nogroup" when they should be nobody:users.

 

I shelled into the dockers and ran "groups nobody" and the output I get is just "nobody".  That should say "users nobody".  So I then executed "usermod -G nobody,users nobody" and restarted the docker.  Now everything is being created as nobody:users as it should.

 

So I'm not sure where this needs to be done, but it looks like the "nobody" user needs to be put into the "users" group somewhere along the way.

 

yes i have been aware of this just not really looked into the fix, im assuming you have created additional users and thus not accessing your shares as user nobody then, yes?. i can include the fix as you detailed, it will take a little while to ripple down though as the fix will be applied at the base image.

 

Thanks, that would be great - no big rush since I know how to fix it.  And yes, it caused issues for me because I have an additional user (which then could not access any of the new directories that had been created under the "nogroup" group).  Maybe another workaround for me would be to add my user into the "nogroup" group, but I hadn't thought to try that that.

 

In the meantime, if anyone else hits this, here's how to fix it:

docker exec -it binhex-sabnzbd usermod -G nobody,users nobody

 

Then restart the docker container.  Repeat for any other dockers (for me, that's Couchpotato and Sickrage).

[binhex]

hi scytherbladez, i have switched the docker over to the standard par2 package, please keep in mind that the "clowns" you refer to is the only guy coding the multithreaded par2 library, this is not an off the wall random link, this is/was the only supported high performance par2 library currently available, so any reference to this in other dockers/plugins will have the same issue.

 

Thanks for the reply. I'm just a bit frustrated since I updated the sab docker I'm questioning whether it's "safe" or even worth "risking" updating dockers now... especially since I couldn't find a way to rollback the update. Learnt a bit about docker, but ultimately achieved nothing.

 

i appreciate the frustration you must be feeling, but i will try my best not to leave anybody "high and dry" with a non working system for too long, real life allowing of course :-)

 

one way to revert back is to copy your existing docker image (as in the docker .img file) before you update, this way you can always revert back to this and you will be back to where you were previously, the other technique is to do with me specifying tags for each release, but this is a major PITA (template and build changes every time ugh) and thus ive not gone down this route, third option of course is to lag a revision behind what im pushing out :-).

[binhex]

 

Now that I know what logging to look at; it looks like authorization my be filing.  I'm 95% sure the user/pass is correct; I just updated them, and can login to the PIA site with them just fine, but I'll investigate more on my end also.

 

If there are any other ideas/issues, I really appreciate the help/feedback.

 

Thanks again.

 

verified my login/pass is correct.  changed to their midwest server; that worked fine.  changed back to east, failed.  changed to midwest, worked.  changed to california, failed.  changed to new york, worked.

 

weird, but means it's likely not a docker problem, but a pia problem.

 

will work with them later today to resolve.

 

thanks again.

 

hm very odd!, thanks for letting me know, let me know what they say, maybe there is a tweak to the ovpn file for certain locations?.

[brisimmons105]

I apologize in advance for the noob question.

I'm having issues getting SAB and Sonarr talking.

 

I'm pretty certain is has to do with my docker folder mappings.

 

Here are screenshots of both my mappings, any idea why they sonar isn't able to find the completed downloads from SAB?

 

[Dimtar]

Here are screenshots of both my mappings, any idea why they sonar isn't able to find the completed downloads from SAB?

 

Does the test SAB work in Sonarr, as in its connecting correctly? What does the log say? Also what does it say when you hover over the orange icon on the activity page?

[brisimmons105]

Thanks Dimtar. The test SAB does work.  They are communicating via the API and Sonarr will send files to SAB, it just can't find them when they are done downloading.

The orange icon says "No files found are eligible for import in 'config/Downloads/complete/filename...'

 

I should mention that the Sonarr library was migrated from my previous plugin to the new docker. This was not started from scratch.

 

EDIT: I should say that I'm fine with starting from scratch if that is the issue, but do the mappings in my docker's seem correct?

[Dimtar]

Can you put up a screenshot of your category settings from SAB? I think that's where the problem is currently.

[brisimmons105]

I removed the TV category form SAB so there weren't issues with Sonarr, but here is a screenshot of the user folders:

[dikkiedirk]

I just have 2 question:

 

Are both port 8080 and 8090 used in the SABNZB docker? Are 2 ports necessary, or can one be removed? I still have unmenu running which uses port 8080. How do I reach the dockerized SAB? My SAB-plugin uses port 8085 and I can reach the plugin through ip-server:8085.

[binhex]

I am having an issue with the permissions of files created by the dockers.  I'm not sure if it's specific to the binhex dockers or just unRaid dockers in general.  But I'm specifically seeing it in the bixhex sabnzbd and sickrage dockers so I'm starting here.

 

What I'm seeing is that all files/directories are being created with an owner of "nobody" and a group of "nogroup" when they should be nobody:users.

 

I shelled into the dockers and ran "groups nobody" and the output I get is just "nobody".  That should say "users nobody".  So I then executed "usermod -G nobody,users nobody" and restarted the docker.  Now everything is being created as nobody:users as it should.

 

So I'm not sure where this needs to be done, but it looks like the "nobody" user needs to be put into the "users" group somewhere along the way.

 

yes i have been aware of this just not really looked into the fix, im assuming you have created additional users and thus not accessing your shares as user nobody then, yes?. i can include the fix as you detailed, it will take a little while to ripple down though as the fix will be applied at the base image.

 

Thanks, that would be great - no big rush since I know how to fix it.  And yes, it caused issues for me because I have an additional user (which then could not access any of the new directories that had been created under the "nogroup" group).  Maybe another workaround for me would be to add my user into the "nogroup" group, but I hadn't thought to try that that.

 

In the meantime, if anyone else hits this, here's how to fix it:

docker exec -it binhex-sabnzbd usermod -G nobody,users nobody

 

Then restart the docker container.  Repeat for any other dockers (for me, that's Couchpotato and Sickrage).

 

ive actually applied the fix this morning, so if you now do a check for updates and then force update for the docker containers your interested in then it should work fine. thanks for reporting this issue, one of the nice side effects of sharing your work is debug by end users 

[binhex]

I just have 2 question:

 

Are both port 8080 and 8090 used in the SABNZB docker? Are 2 ports necessary, or can one be removed? I still have unmenu running which uses port 8080. How do I reach the dockerized SAB? My SAB-plugin uses port 8085 and I can reach the plugin through ip-server:8085.

 

8080 is used for http and 8090 is https, one of these ports could be removed once you have decided which one you want to use, however its trivial to just change the "host port" number so it doesnt clash with any other dockers as opposed to removing the port, so for example this is my port mappings for that docker container:-

 

 

as you can see ive got specific ports i use on the host side, this prevents any clashes, i keep a text file which lists all port mappings on the host side and what they map to on the container side, also an indication as to whether i port forward these on my router, granted a little bit of admin but its fairly easy to keep up to date.

 

 

[dikkiedirk]

I just have 2 question:

 

Are both port 8080 and 8090 used in the SABNZB docker? Are 2 ports necessary, or can one be removed? I still have unmenu running which uses port 8080. How do I reach the dockerized SAB? My SAB-plugin uses port 8085 and I can reach the plugin through ip-server:8085.

 

8080 is used for http and 8090 is https, one of these ports could be removed once you have decided which one you want to use, however its trivial to just change the "host port" number so it doesnt clash with any other dockers as opposed to removing the port, so for example this is my port mappings for that docker container:-

 

 

as you can see ive got specific ports i use on the host side, this prevents any clashes, i keep a text file which lists all port mappings on the host side and what they map to on the container side, also an indication as to whether i port forward these on my router, granted a little bit of admin but its fairly easy to keep up to date.

 

If you want to setup and configure sab or check what is downloading, you just type ip-server:1400 or ip-server:8080?

[binhex]

I just have 2 question:

 

Are both port 8080 and 8090 used in the SABNZB docker? Are 2 ports necessary, or can one be removed? I still have unmenu running which uses port 8080. How do I reach the dockerized SAB? My SAB-plugin uses port 8085 and I can reach the plugin through ip-server:8085.

 

8080 is used for http and 8090 is https, one of these ports could be removed once you have decided which one you want to use, however its trivial to just change the "host port" number so it doesnt clash with any other dockers as opposed to removing the port, so for example this is my port mappings for that docker container:-

 

 

as you can see ive got specific ports i use on the host side, this prevents any clashes, i keep a text file which lists all port mappings on the host side and what they map to on the container side, also an indication as to whether i port forward these on my router, granted a little bit of admin but its fairly easy to keep up to date.

 

If you want to setup and configure sab or check what is downloading, you just type ip-server:1400 or ip-server:8080?

 

<unraid server ip>:<host port mapping>

 

e.g. http://192.168.1.10:1400

[ThatDude]

Is this the right thread to get help with binhex-get-iplayer?

 

I have it installed ok, have edited the 'showlist' file as follows:

 

#!/bin/bash
# the list of shows to download
SHOWLIST="1526"

 

Which should in theory download an episode of 'Have I got news for you'.

 

I've restarted the docker to have it read the updated showlist but it fails, the relevant part of the debug log looks like this:

 

2015-06-21 11:23:55,425 DEBG 'get-iplayer' stdout output:
Matches:
1526:	Have I Got a Bit More News for You: Series 49 - Episode 9, BBC One Cambridgeshire, , default

INFO: 1 Matching Programmes

2015-06-21 11:23:55,437 DEBG 'get-iplayer' stdout output:
WARNING: Please download and run latest installer or install the XML::Simple Perl module for more accurate programme metadata.

2015-06-21 11:23:55,562 DEBG 'get-iplayer' stdout output:
ERROR: Failed to get version pid metadata from iplayer site

 

I guess the docker needs an update to include the latest XML Perl module (whatever that is)  :-)

 

im afraid get-iplayer is currently broken, bbc changed their feeds and it broke get-iplayer for now, i think the devs are looking into it, so i will post back here once its fixed.

 

I think they fixed it on Arch: https://aur.archlinux.org/packages/get_iplayer/

 

The technology itself works fine, I'm downloading content using the Mac GUI version right now.

[binhex]

Is this the right thread to get help with binhex-get-iplayer?

 

I have it installed ok, have edited the 'showlist' file as follows:

 

#!/bin/bash
# the list of shows to download
SHOWLIST="1526"

 

Which should in theory download an episode of 'Have I got news for you'.

 

I've restarted the docker to have it read the updated showlist but it fails, the relevant part of the debug log looks like this:

 

2015-06-21 11:23:55,425 DEBG 'get-iplayer' stdout output:
Matches:
1526:	Have I Got a Bit More News for You: Series 49 - Episode 9, BBC One Cambridgeshire, , default

INFO: 1 Matching Programmes

2015-06-21 11:23:55,437 DEBG 'get-iplayer' stdout output:
WARNING: Please download and run latest installer or install the XML::Simple Perl module for more accurate programme metadata.

2015-06-21 11:23:55,562 DEBG 'get-iplayer' stdout output:
ERROR: Failed to get version pid metadata from iplayer site

 

I guess the docker needs an update to include the latest XML Perl module (whatever that is)  :-)

 

im afraid get-iplayer is currently broken, bbc changed their feeds and it broke get-iplayer for now, i think the devs are looking into it, so i will post back here once its fixed.

 

I think they fixed it on Arch: https://aur.archlinux.org/packages/get_iplayer/

 

The technology itself works fine, I'm downloading content using the Mac GUI version right now.

 

Your right it looks like it's now fixed, yay, tweaked the docker a bit rebuilt it and it's now working, so please update and let me know.

[binhex]

I have been playing with the TeamSpeak server.

 

As previously mentioned, doesn't look like it is picking up the license file. I don't think certain functions are actually being saved. I set a password for the server, but you can use any password, or none. Doesn't matter. Just let's you connect. Seems to save my channel config, but that is about all??

 

i will take a look at this next week for you, i dont have a licence file so i cant really test that side of things, but i can test the saving of settings, i will post back with my findings

 

Ok, well I removed the container and image and reinstalled it. Definitely did something different this time. Looks to be saving changes and also enforcing password. But, still will not pick up my license file. Tried another TS docker (crap one but tried for testing) and their implementation did pick up my file.

 

PM if you would like me to send the key file to you for testing.

 

Yeah I'm going to need to borrow your licence file if you want me to debug the issue, please send me a pm with a link and I will do some testing.

[sparklyballs]

Can i ask you  a completely unrelated question to your containers about iptables ?

[binhex]

Can i ask you  a completely unrelated question to your containers about iptables ?

 

Of course! shoot

[sparklyballs]

Can i ask you  a completely unrelated question to your containers about iptables ?

 

Of course! shoot

 

i'm trying to make a mythtv container fly and would really like to keep it as network type bridge to make mythweb easier.

 

however it seems that hdhomerun doesn't want to work unless host is set.

 

i believe the issue is this.

 

https://code.mythtv.org/trac/ticket/7272

 

but i don't know how to implement it for a test build.

[binhex]

Can i ask you  a completely unrelated question to your containers about iptables ?

 

Of course! shoot

 

i'm trying to make a mythtv container fly and would really like to keep it as network type bridge to make mythweb easier.

 

however it seems that hdhomerun doesn't want to work unless host is set.

 

i believe the issue is this.

 

https://code.mythtv.org/trac/ticket/7272

 

but i don't know how to implement it for a test build.

 

hmm ok, well unless the docker image has the firewall defined (via iptable entries) then i doubt this is the issue, did you see this is also marked as invalid? if you type iptables -L when the mythtv docker container is running what does it show? im assuming just the default ACCEPT for the 3 iptable rule sets?