needo

Containers aren't supposed to be upgraded, only images are. Containers are temporary.

Perfect point. Let's bring the post back on topic of the Docks and software requests. Sent from my SM-N900V using Tapatalk

If this will get us around the issue of updating/restarting the apps without having restart the container then I am all for it. I do not support updating live apps. It's a recipe for disaster.

I am seriously considering making the jump and converting everything to phusion/baseimage. Based on what I have learned in the [POLL] thread. Any strong thoughts one way or the other?

Updating an application within a Docker container via a web interface goes against the whole point of running Docker in the first place. Lets say you update Sickbeard via the web interface. Then something happens and you need to regenerate your container. There goes your update, and your current database that was upgraded earlier is no longer compatible with the old version. Best case scenario SickBeard is offline, worst case scenario the database is corrupted and you have to now start from scratch. Just Say No to git and updating via Web UI in Docker!

Updating an application within a Docker container via a web interface goes against the whole point of running Docker in the first place. Lets say you update Sickbeard via the web interface. Then something happens and you need to regenerate your container. There goes your update, and your current database that was upgraded earlier is no longer compatible with the old version. Best case scenario SickBeard is offline, worst case scenario the database is corrupted and you have to now start from scratch. Just Say No to git and updating via Web UI in Docker!

Unless you have mounted "/mnt/user/Files/Downloads" in Docker it is moving it within the container itself. If you add -v /mnt/user/Files/Downloads:/mnt/user/Files/Downloads it should fix your issue.

5.5 Any chance you can do a 10.0.10 version? I'll see what I can do.

Odd. That means it is running and accepting connections. Mine looks identical to yours.

I was wrong. For couchpotato to talk to Plex please add --net="host" to the docker run line for CouchPotato.

With nzbget running if you run: netstat -anp | grep 6789 What returns?

5.5

You connect at http://Tower:6789 (Or whatever your unRAID is called)

unRAID does not support apt-get.

In your docker run command you specify: -v /mnt/user:/downloads It's creating the downloads where you told them to. That really should be -v /mnt/cache/downloads:/downloads (If you have a cache drive)

Please try it now.

So odd. This works perfectly on my unRAID systems. New version building now.

CHANGELOG 06/24/2014 (deluge) Opened up the server port Added PlexConnect: https://registry.hub.docker.com/u/needo/plexconnect/ Added mariadb: https://registry.hub.docker.com/u/needo/mariadb/ (nzbget) Generate nzbget.conf and downloads directory on a new install.

The default username is nzbget and the password is tegbzn6789 you will then need to configure nzbget to fit your environment. I don't get a prompt for username or password. Error: 503 Service Unavailable and when i try to get the logs root@UNRAID:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 68545aeb08d7 needo/nzbget:latest /bin/bash /start.sh 10 minutes ago Up 10 minutes nzbget root@UNRAID:~# docker logs nzbget /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory /downloads/dst/nzbget.log: No such file or directory root@UNRAID:~# I'll post a fix in a few. I see where it can be improved.

I only opened up the web-ui port for delgue and not the server port for other clients to connect. I will post an update today which will open that up. I am still working on a transmission docker but it is taking awhile, deluge was easier to turn into a dock.

The default username is nzbget and the password is tegbzn6789 you will then need to configure nzbget to fit your environment.

If using nzbget for the first time please download this sample configuration file, rename it to nzbget.conf and put it in /path/to/dir/with/nzbget.conf/ - https://raw.githubusercontent.com/needo37/nzbget/master/nzbget.conf.sample

Could you please post what docker logs nzbget says? Thank you. hate to be igorant but where is the location of these logs Not at all it is actually the command: docker logs nzbget

Could you please post what docker logs nzbget says? Thank you.

That is normal and expected behavior. When executing a test of Plex from sickbeard/couchpotato theya ssume that Plex is running on a desktop with a client all on the same machine. With unRAID this is not the case so the test errors witha 401. However when actually processing a movie or TV show it will update Plex correctly.