binhex

reserved

Overview: Support for Docker image arch-sabnzbd in the binhex repo. Application: SABnzbd - http://sabnzbd.org/ Docker Hub: https://hub.docker.com/r/binhex/arch-sabnzbd/ GitHub: https://github.com/binhex/arch-sabnzbd Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

reserved

IMPORTANT - Deluge 2.x compatibility issues There is currently an issue with radarr connecting to deluge 2.x, they havent got support in place for deluge 2.x yet, sonarr looks to have some basic support in place but there may still be some small issues. see here for issue for radarr:- https://github.com/Radarr/Radarr/issues/3562 see here for issue for sonarr:- https://github.com/Sonarr/Sonarr/issues/2412 According to a post on the sonarr issue thread, this is the problem in a nutshell:- https://github.com/Sonarr/Sonarr/issues/2412#issuecomment-469070076 couchpotato at this time looks to be unable to communicate with deluge 2.x (even against latest commits to master), no information shown in log, even if logging level set to debug. There is also the possibility that private trackers have not vetted deluge 2.x as a torrent client and thus it may not be permitted at this time (check with your private site admin). if you wish to rollback to Deluge 1.x then follow Q5. from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Overview: Support for Docker image arch-deluge in the binhex repo. Application: Deluge - http://deluge-torrent.org/ Docker Hub: https://hub.docker.com/r/binhex/arch-deluge/ GitHub: https://github.com/binhex/arch-deluge Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

IMPORTANT - Deluge 2.x compatibility issues Deluge v2.x has now been released, as this is a MAJOR code re-write certain things will currently not work until they are re-coded:- Couchpotato at this time looks to be unable to communicate with deluge 2.x (even against latest commits to master), no information shown in log, even if logging level set to debug. The current workaround is to use blackhole/watch folder and get Deluge v2.x to pickup torrents from there. As Deluge v2.x is re-written for Python 3.x the current Deluge v1.x plugins will NOT work with Deluge v2.x until they have been re-coded, thus if you rely on specific 3rd party Deluge plugins then you may want to roll back to Deluge v1.x (see below for how to do this). There is currently no Deluge thin client v2.x for Mac or Windows, and Deluge 1.x thin clients cannot communicate with Deluge v2.x server, if you are using the thin client from either of these platforms then currently you will have to rollback to Deluge v1.x to be able to connect (see below for how to do this). Private trackers may not of vetted deluge 2.x as a torrent client and thus it may not be permitted to connect to the track at this time (check with your private site admin). if you wish to rollback to Deluge 1.x then follow Q5. from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

OpenVPN support for PIA 'next-gen' network is now in, see Q19 for how to switch from legacy network to next-gen in the link below Multi remote endpoint support is now in see Q20 for how to define multiple endpoints (OpenVPN only) in the link below WireGuard support is now included, see Q21 for how to switch from OpenVPN to WireGuard in the link below https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Overview: Support for Docker image arch-delugevpn in the binhex repo. Application: Deluge - http://deluge-torrent.org/ Docker Hub: https://hub.docker.com/r/binhex/arch-delugevpn/ GitHub: https://github.com/binhex/arch-delugevpn Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

Important - This thread is NOT for support of Docker images, please use the separate support threads shown in the "Docker Images" section shown further down. Overview: Support of unRAID Docker templates, news and user requests for new Docker images for the binhex Docker repository. Docker Hub: https://hub.docker.com/u/binhex/ GitHub: https://github.com/binhex If you appreciate my work, then please consider buying me a beer Description All the Docker images contained within this repository are Arch Linux based, the reason i choose Arch is as follows:- Cutting Edge - Packages are latest stable versions, thus you get no issues with old packages causing issues with newer apps. Small Footprint - Arch is built with a minimal approach, including only the required packages for the OS. Arch User Repository (AUR) is vast! - AUR has packages for nearly every popular linux application out there, and using a helper app like packer means simple and quick deployment of virtually any application as a docker. Familiar OS - Working knowledge of Arch, based on past experience running Arch Linux in a VM. Installation OK, sounds good to me, so how do i install your Docker apps using unRAID?. Whilst you can still use the steps shown above, it's now recommended to install the excellent Community Application (CA) plugin instead, see here for instructions and support:- https://forums.unraid.net/topic/38582-plug-in-community-applications/ Firstly you need to be running unRAID ver 6.0.0 or later, once installed follow the instructions below:- Navigate to "Docker" tab and then the "Docker Repositories" sub-tab in the unRAID webui Enter in a URL of https://github.com/binhex/docker-templates in the "Template repositories" field Click on the "Save" button Click back to "Docker" tab and then click on the "Add Container" button Click on the "Template" dropdown menu and select the desired Docker image Click the "Advanced View" toggle on the top right and fill in required fields e.g. volume data, environment variables etc Click on the "Create" button at the bottom of the window to begin pulling down the Docker image Once the image is downloaded you should see it appear in the "Docker Containers" sub-tab Docker Images [Support] AirSonic [Support] CouchPotato [Support] Deluge [Support] DelugeVPN [Support] Emby [Support] get_iplayer [Support] IntelliJ [Support] Jackett [Support] Jellyfin [Support] Jenkins [Support] Krusader [Support] LibreOffice [Support] Libresonic [Support] Lidarr [Support] Madsonic [Support] Medusa [Support] MiniDLNA [Support] MovieGrabber [Support] NZBGet [Support] NZBHydra [Support] NZBHydra2 [Support] Plex [Support] PlexPass [Support] PyCharm [Support] qBittorrentVPN [Support] Radarr [Support] Rider [Support] rTorrentVPN [Support] SABnzbd [Support] SABnzbdVPN [Support] Sickbeard [Support] Sickrage [Support] Sonarr [Support] Teamspeak [Support] Tvheadend Scripts [Support] no_ransom Key: Green - application/docker container confirmed working, no known issues Orange - application/docker container under heavy development Red - application/docker container broken or not working as expected Documentation https://github.com/binhex/documentation

In reply #84? Lol yeah that's the one, damn this thread moves quickly :-)

I would suggest either using the command line script I posted a dozen or so posts back, or if the growth of the image file is relatively quick then use the classic I.T. trick of divide and conquer, so shutdown half your dockers, if growth continues then you know the problem is with the half you have running, if it doesn't continue then the issue is with the half shutdown, simply keep doing this until you fund the troublesome docker.

+1 for the above, I understand the convenience of auto updates, but I think it can come at quite a high price, the dockers I produce will never include code to auto update.

Thanks Binhex, I used this command to find anything over 1GB. The container that starts with e93 is binhex/sonarr, but I am unable to find any dockers that start with 92e. Is there something I am missing here? I am searching by using docker ps -a command. /var/lib/docker/btrfs/subvolumes/92e0d85384a0b19ed2dc7c91e6c2471f66d7f08b1c4905c642ee6c09a3e34b12/The: 993M /var/lib/docker/btrfs/subvolumes/92e0d85384a0b19ed2dc7c91e6c2471f66d7f08b1c4905c642ee6c09a3e34b12/The: 1.2G /var/lib/docker/btrfs/subvolumes/92e0d85384a0b19ed2dc7c91e6c2471f66d7f08b1c4905c642ee6c09a3e34b12/The: 2.8G /var/lib/docker/btrfs/subvolumes/92e0d85384a0b19ed2dc7c91e6c2471f66d7f08b1c4905c642ee6c09a3e34b12/The: 2.7G /var/lib/docker/btrfs/subvolumes/92e0d85384a0b19ed2dc7c91e6c2471f66d7f08b1c4905c642ee6c09a3e34b12/The: 1.1G /var/lib/docker/btrfs/subvolumes/e93e17d188f4b6ef2916abf382b43e3ed490c616477db527b15f846d8b80d56e/The: 2.7G UPDATE: I looked for any files over 50M in that container and added up the files and I am already at almost 20G. This seems to be the culprit of my growing docker size. How can I find out what container this is? UPDATE #2: Apparently this is a known issue with subvolumes not getting deleted properly. According to the following https://github.com/docker/docker/pull/15801 is should be fixed with Docker 1.9. Does anyone know if this will be in unRAID 6.2? hmm interesting bug raised there, could explain growing unraid docker image size if a user is doing a lot of churn, i.e. creating and deleting docker containers, still doesnt cover the case where people are seeing usage grow whilst not doing any creation/deletion of containers (just to be clear im NOT seeing this <-).

no, we are using btrfs, not devicemapper, and what brit said :-)

just incase anybody is interested, the way i configure the transcode directory for the plex and plex pass images i create is simply to set the environment variable to point at the chosen folder, in this case i just create a tmp folder under /config and get it to store temporary transcode files in there, link to (old) article showing this:- https://support.plex.tv/hc/en-us/articles/200273978-Linux-User-and-Storage-configuration as for tracking down unruly docker containers, i did once have to debug an issue with miniDLNA creating a VERY large log file inside the container, one of the techniques i used to track it down was to search the loopback mounted docker image for large files:- find /var/lib/docker/btrfs -type f -size +50000k -exec ls -lh {} \; | awk '{ print $9 ": " $5 }' the above will display all files 50MB or larger, the container id is shown in the path, as well as the file system in the docker container, with a bit more work somebody could easily map the container id in the path to the friendly name of the container for a more human friendly result :-).

add me to the list of people with this issue, running 6.1.3, i do have a running vm, as well of course a few dockers :-), syslog attached. here is the message im recieving (ssh in using putty):- Message from syslogd@Tower at Oct 4 22:38:20 ... kernel:unregister_netdevice: waiting for lo to become free. Usage count = 1 Message from syslogd@Tower at Oct 4 22:38:30 ... kernel:unregister_netdevice: waiting for lo to become free. Usage count = 1 syslog-2015100500.zip

The repo is fully supported (as are the containers we are adding). However, support is limited to getting the container running and accessible, not configuring Plex from within it. We also do not yet support migrating to this container from a Plugin. Some may be able to get that to work, but we do not have a step-by-step guide on how to do it at this point. I would suggest the OP is updated to reflect this then as this sets this repo above all others Or below all others :-) I think most devs here will support basic configuration of the application running, or am I being too kind? ;-)

the other rather nasty issue i found is that if you fill up your docker image file (not to be confused with docker images) then ive seen it where on a restart most/all of your docker containers will not start, if you click on advanced view you can see the containers but its not possible to start them, solution is unfortunately to stop docker, delete docker image file, start docker, re-pull everything down, ive seen this twice now so its def an issue. wouldnt mind so much if there was a way to free up space after deleting images/containers but there isnt, at least not to my knowledge.

Last time I checked you do need to enter in details to pull down plex pass version but it doesn't check so it can be anything.

I like supervisor a lot and use it for all my docker images, however I must make you aware it lacks one important feature and that's dependency management. There is a long standing request for this, hoping it gets included soon.

Excellent! Please let me know how you get on, quick word of warning, whilst I have tested this extensively and run it against my own media collection (approx 1000 movies), I would advise that you copy a few movies to a test area and make sure the resulting files are what you expected. Any feature requests also welcome. binhex.

Hi guys, i have created a Python script to remove unwanted audio and subtitle tracks from Matroska container formatted files, the script uses mkvmerge (from mkvtoolnix) to identify and then remove unwanted audio and subtitles. The reason for wanting to do this is file size, i have run this script across my media library and it did save a fair amount of space (approx 100GB), i now also run this on any new media i have recently acquired. So without further ado here is a link to it, you will find the installation, syntax and examples here:- link to prereq's and usage:- https://github.com/binhex/videoslimmer link to source here:- https://github.com/binhex/videoslimmer/releases Let me know how you get on with it, any questions please post here and i will get back to you.

For me the whole idea of docker is repeatable distributed code, once you start messing with this and having dockers which can update themselves, or having special "edge" flags to trigger different branches of code then it stops being docker and becomes something else, something IMHO that cannot easily be supported and is more prone to breakage. i prefer solving the following using this methodology instead:- 1. updating docker images - use a shared github repository that multiple "trusted" community members have admin access to in order to maintain the dockerfiles for new releases, this would reduce the time a user has to wait in order to run the latest stable version. 2. unstable/stable applications - have these as separate docker images, clearly marked as stable/unstable, yes this means more docker images and thus potentially more overhead but in the long run i believe this will reduce the amount of time required to support these images by reducing complexity and by splitting the two you also reduce the risk of complex bash scripts causing issues for users who just want to run a simple stable version. hey just my thoughts, please feel free to ignore :-).

agreed.

hi joelones, i think your issue is related to the fact your running docker in a vm and then trying to access host resources, this is basically doing two hops, one hop to get from the docker networking stack to the vm, and then another hop to go from kvm/xen networking stack to the unraid host. i think this is what is causing your issues, i personally would recommend running docker bare metal on unraid and not in a vm, as this is the way it was designed to work, im not sure if you will be able to punch all the way through two levels of virtualisation with any sort of reliability.