ironicbadger

Feel free to head over freenode #linuxserver.io to tell us what you want in a bit more detail...

Try nzbget. The guys badgered me into doing so and I haven't looked back. I used Sab for 4+ years stubbornly. We do have a Sab docker already, just not released yet BTW.

Good morning all! Today's announcement is that Sparklyballs has joined our ranks. He will be a great addition to the team.

Am I missing something? checkout doesn't do a pull, it is a local operation.

A good way to tell is to look at how the auto updates are handled upon startup. For most of our containers this is handled with a script like this... https://github.com/linuxserver/couchpotato/blob/master/init/20_update.sh You can see here that if the code doesn't exist, it is fetched from github. The rest therefore is handled by the auto updater in the app. If the init script looks like this one though, ie 'apt-get update...' Then its a container restart which is required. https://github.com/linuxserver/smokeping/blob/master/init/90_update_apt.sh So in short, there's no way to know without looking under the hood which app updates with which method. Unless we added that to the descriptions...

Sonarr gui

i have sparklyballs, not crystal ones, lol. it has a different database schema for sure, but i'm not gonna make any predictions until isengard goes final. LOL So I guess it might be simpler to just run MariaDB separate?

Some more questions lately in IRC about why you'd want to use Smokeping. This episode of the Linux Action Show covers it in quite some detail, skip to 7 mins. http://www.jupiterbroadcasting.com/46487/opensuse-13-1-review-las-29e07/

Question regarding Koma. What happens when ISENGARD comes out? I've been bitten by version upgrades not playing nice with the DB before.

Oops. I got confused as to which thread I was in on my phone. Apologies all!

Just wanted to announce a couple of new contributors to the LinuxServer.io community. kode - the fanart.tv guy who's working on Aesir, a new unRAID webUI smdion - well, you know him already but he's contributed dozens of Docker's to date but is converting his existing fleet to be under the LinuxServer maintenance umbrella. Welcome to the team guys! What is LinuxServer.io? Well, it started out life as my personal blog (blog.ktz.me) and then morphed into a community based site with articles about how to do things on a Linux Server aimed at the home user. Since then, lonix, j0nnymoe and I have migrated back to unRAID and converted our existing Docker's to truly platform agnostic whilst supporting unRAID. Now, we're just a group a chaps who hangout in IRC (@freenode.net #linuxserver.io). We're looking for contributors to various projects including Docker containers, Aesir and authors for posts and content on the main blog itself. We also have our own forums at forum.linuxserver.io if you want to take a peak. The idea is, if we can get a group of people passionate about Docker all pulling in the same direction, amazing things can and will happen. More the merrier!

I don't think this is (or should be) the thread to ask for support. Go to the repo maintainers or app specific thread for support. I find myself often thinking when reading posts here "which container are you running?" and many other generic questions.

No need for a Docker. Just use screen and SSH with rsync. You can get fancy and do dry runs before you run the real command to check what you're about to do but this will copy all files in one dir to another via an encrypted SSH session. e.g. rsync -avz -e ssh [email protected]:/location/of/remote/dir /mnt/user/unraid/share/where/you/want/to/store/stuff

Given the regularity and the time frames in question that had to be the only solution. Glad it's sorted.

/config in the app logs refers to the location inside the container. Where are you mapping this too outside the container? are the permissions correct on this folder? Etc.

Looking through your logs a second time I notice that it complains about not being able to find config dir. Is your cache drive reliable? Is your docker.IMG corrupt? Have you deleted and redownloaded the container. That line makes me suspect something like a hardware issue rather than an issue with this container.

That is strange, I've been running this Docker for over a year now without any issues such as you describe. I do experience the thumbnail issue from time to time but this isn't exclusive to Dockers, I've had this when installed as a plugin or whatever so I presume its a foible (feature) of CP. Perhaps you would share your experience over at the CP site? Also here please share you couchpotato.INI and tell us the settings you added the container with.

Anyone? Firstly, double posting like this is lame. Just be patient. Second, shouldn't you be posting in the Plex docker you are usings support thread / repo thread? Third did you add your array to the container when you created it? Ie mount point /movies pointing to /mnt/user/movies or whatever?

Yes I agree. I am a little surprised that v6 didn't include more documentation or community reorganisation. I'm glad that v6 final is out but the code is half the product.

Super, super useful stuff guys. Top notch.

kode, our newest contributor at linuxserver.io just wrote a pertinent article you might find interesting if you're a plugin dev. http://www.linuxserver.io/index.php/2015/07/08/unraid-plugin-authors-automate-the-plg-process-after-committing-to-github/

Easy, we already have a Sab image that lonix made. Can convert it to be an alpha/beta friendly version I'm sure.

He he sorry smdion. The king is dead, long live the king.

What we meant was that the plex app updates on container restart. We (both lonix and I) update the file in question within 4 hours max of a plex release but usually a lot less. All the user need do is restart the container. Now, the issue with plex specifically is the handling of auto update for plexpass. It's not easily possible to automate that yet but the not pass version is easy with relying on a third party service (baconater) like he does I think.

Go to the port you specified with the following suffix http://192.168.x.x:8080/cgi-bin/smokeping.cgi You'll be able to edit the targets which get pinged in the Targets file which lives in /config (stored in appdata)