binhex

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.

Hi joelones no expert on using apt-get but I think that should be python2 not python2.7

just to chime in the Kingston MobileLiteG2 does indeed work fine for me, been running with this for just over a year now with no issues, i have heard reported issues of the newer usb 3.0 version of this NOT working correctly though, possibly due to motherboard and/or unraid driver support for usb 3.0, link:- http://www.amazon.co.uk/Kingston-Technology-Multi-Card-Reader/dp/B007PFQ0PC

Did you try this: http://lime-technology.com/forum/index.php?topic=31297.0 ? I will create a badass PXE Server that uses Tiny Core Linux and a HTTP Server (faster than tftpboot) for Menus and isos / images. I will work on it tomorrow and post it for all of you to test. Perhaps gfjardim wouldn't mind creating a slick WebGUI for adding / removing images and configuring the PXE Menu. I can get it close but he will need to take it the last mile. NOTE: I am not going to support this long term so one of you will have to take it and own it. Looking forward to this!

Surely the slow browsing is just due to NetBIOS lookup? Add tower to your windows hosts file if you still want to use tower without the performance hit, or better still setup your own name server. Sent from my Nexus 7 using Tapatalk

I too had the exact same issue as peterb post #635, with all flags being ignored when started via go script, so there is def something odd going on when started via go script. Sent from my Nexus 7 using Tapatalk

many thanks for posting that itimpi, one last question, what is your current memory usage for cache-dirs?

yes i did see that suggestion earlier in this thread and had done that in the script before adding to go file and rebooting, still caused nasty OOM and crash. i take it you are running it now?, if so what flags are you using and are you running this via go file or manually starting after unraid has booted?.

hey neo_x, interested in this:- i did run cache-dirs via go script, i found it consumed all resources on my server and basically killed dom0 and all domU's after approx 2 days, what issue were you seeing when starting it via go script, high memory consumption, or something else?. i have of course stayed away from running cache-dirs for the time being after that experience, can anybody confirm they have this running stable on v6 and if so what flags they are using. cheers. binhex. p.s nice to see ya on another board :-)

ok so im of the if it aint broke don't fix it brigade, but wondered if there is anything significant i should be worried about in P16 and P17 LSI firmware versions, as my M1015 IBM MegaRaid cards are currently cross flashed to P15 and working happily. so has anybody found any issues with P15?

ditch that drive, if its still got 6 pending sectors after 2 pre-clears there is little to no chance its every going to go to 0, i personally wouldn't even let that drive be within 30 metres of my array :-) the question you got to ask yourself, is even if it did go to 0 would you REALLY want to chance it, possibly if it went to 0 after 1 pre-clear. "Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 6"