lonix

It should work on all images Sent from my iPhone using Tapatalk

Same error here since today's nzbget docker container update. EDIT: It appears unrar and 7za are in the /app directory. An alternate temporary solution is to change Settings -> unpack -> UnrarCmd to /app/unrar and SevenZipCmd to /app/7za I shall investigate.

So does that mean that there is no way to set the transcode directory to memory (i.e. /tmp)? I have been debating switching from ESXi to bare metal, and that is something I'd love to keep since it reduces wear on my SSDs... It's forced by plex not by us. We just adapted our config

Plex will now force you to transcode to /config and thus the problem we where trying to avoid is fixed thus we do not need this mapping anymore Sent from my iPhone using Tapatalk

You observed corret. I will look into your use case

https://www.linuxserver.io/index.php/2016/04/07/changes-to-our-plex-docker-container/ Clarification on changes

Hey guys, due to a agreement with plexDevs we decided to turn off the ability to install plexpass versions in our container. (more comming on linuxserver.io). You can either use -e VERSION=0.9.<restofversionnumber> or wait untill our container updates. (once this PR gets merged: https://github.com/linuxserver/docker-plex/pull/32) The container update should enable "plexpass updates" again. and will be acompanied with a article on our website. Thanks for the understanding. And for useing linuxserver.io's containers. we love makeing them for you all.

your welcome mate

Restart the container, that is the only way that is recommended. Nevermind.. that wasn't the issue.. the little tiny "Advanced View" slider that I had not seen. Just flipped it and found the variables and now all is well. Thanks anyway! You dont need to set the version at all, the container will update plex itself to latest version when you start the container up, thus restart=update

interesting, let me look into it.

Please update the container please reboot the container

How do I go about updating manually? Restart the docker container, it will update automaticly

Try setting the version again, it looked like it was missing. (screenshot the setting)

The ui will eventually tell you, but the way I know it is via subscribing to the release thread forums

Yes mine is working perfectly.

Mike install Community Applications plugin and all will become much much clearer.... Like he said. CHBMB is just too quick for me! Darling... Is that you? ^^ slut That means Stop in Norwegian (At least almost) Well its acctually closer to the swedish Stop than the Norwegian.

probably

wait do you want updates or not ?

I recently converted from Needos to the Linuxserver Plex docker. My only issue was waiting long enough after starting the Linuxserver Plex docker for the first time, it took about 5 minutes or so before I could access Plex. I think the docker may have been scanning (or changing file permissions or something) on my huge Plex metadata database. But all my setup and watched status all transferred flawlessly. yea the first time you start we fix the library to be more standard

It Should go fairly easy, there should be a guide thingy on our website

I'm not actually to far from adding something like this. But I'm currently looking at a advanced feature set that might happen. I will let you know if that happens

It will update when the server starts up as the docker service and ergo all the containers will be restarted. As regards the auto-updating we make comment of this on the first line of our docker hub page that is linked on the first page of this thread. Ah...Good to know as that could become an issue if it updates and for whatever reason the update may not be wanted. I have, guess like you all have, seen some bad updates come out. Even Kodi had some poor released right down to video or audio stopping. I am guessing there is not a way in your containers to turn that off so it only looks when you tell it to or click on RESTART vs just doing it on every load? But then again, maybe it is not as bad as I am thinking it could be. I am just basing it on history of some updates that broke things. Thanks again for the help. I'll probably get spanked by linuxserver for saying this, but you are correct... Occasionally (thankfully not often) auto updates can cause problems with the program not working correctly. If you want to avoid auto updates, then you're probably going to have to switch to binhex's versions (but then you'll be a couple of versions behind). Myself, I run a mixture of containers from the various authors, and I absolutely love the support from linuxserver, but also have some reservations about the auto update features. But, that hasn't stopped me from running a few of their containers. You wont get spanked for giving your opinion. You are even right.Automaticly updateing the core apps (the app the container is about) is and always has been a "risk" a chance or a gamble if you will. however considering the 40+ containers we have, that has happened a total of 2 times the last year or so. 1. was a broken couchpotato. (fixed in less than 24 hours) 2. Was some users haveing trubble with the "new transcode" in plex. (we allready supply pickable version for that container) (fixed in 4 days). Anyhow here is the thing. When i first started the container collective (the one that turned into linuxserver.io), i had to choose how i wanted to approach these containers. Automatically updating the containers certainly had its downside. - A update could break the intended software. - And even worse, it could ruin what we call "appdata" for the user. Not automatically updating would mean: - I would have to monitor all the software's for new versions to avoid noise from anyone complaining about the "old" containers. - I would have to test every single update to ensure it did not break anything (because if a human build it, it can't go wrong) - If i do happen to publish anything with broken stuff, people would yell at me. (I don't like that) This\docker\i\myteam has since evolved a bit and we are always open to suggestions. and somewhat change. The current idea regarding automatic updates, if we find a problem (like with the plex thingy) we will look for a way to give users a static option for that container. (I am also looking into making general purpose no-update setting) But one thing that will never change is the philosophy behind our primary containers. Up-to-date, High quality\avalibilty, and great support.

Please make a issue on github. And I'll look into it tomorrow.

Try mapping it to /downloads ---> /mnt/user/appdata/SABnzbd/downloads The /downloads mapping must be identical on all containers

It gives the container access to the hardware clock