[Support] Linuxserver.io - SABnzbd


Recommended Posts

And it seems now I know why Sonarr was not updating either.  It is also broken. 

 

From what I read, this information comes from the container files. If this is the case, and I am not sure, that could mean both of the containers for Sonarr and SABnzbd are no longer valid. They will install, but can not update.  Both of my containers came from Lunuxserver.io.

 

Anyone?  This surely is not a good thing.

 

Sonarr restart....

 

*** Running /etc/my_init.d/20_apt_update.sh...

We are now refreshing packages from apt repositorys, this *may* take a while

W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/restricted/source/Sources  404  Not Found [Mirror: http://mirrors.syringanetworks.net/ubuntu-archive/]

 

W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/universe/source/Sources  404  Not Found [Mirror: http://mirrors.syringanetworks.net/ubuntu-archive/]

 

W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/multiverse/source/Sources  404  Not Found [Mirror: http://mirrors.syringanetworks.net/ubuntu-archive/]

 

W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/main/binary-amd64/Packages  404  Not Found [Mirror: http://mirrors.syringanetworks.net/ubuntu-archive/]

 

E: Some index files failed to download. They have been ignored, or old ones used instead.

Link to comment

And it seems now I know why Sonarr was not updating either.  It is also broken. 

 

From what I read, this information comes from the container files. If this is the case, and I am not sure, that could mean both of the containers for Sonarr and SABnzbd are no longer valid. They will install, but can not update.  Both of my containers came from Lunuxserver.io.

 

Anyone?  This surely is not a good thing.

 

Sonarr restart....

 

*** Running /etc/my_init.d/20_apt_update.sh...

We are now refreshing packages from apt repositorys, this *may* take a while

W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/restricted/source/Sources  404  Not Found [Mirror: http://mirrors.syringanetworks.net/ubuntu-archive/]

 

W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/universe/source/Sources  404  Not Found [Mirror: http://mirrors.syringanetworks.net/ubuntu-archive/]

 

W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/multiverse/source/Sources  404  Not Found [Mirror: http://mirrors.syringanetworks.net/ubuntu-archive/]

 

W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/main/binary-amd64/Packages  404  Not Found [Mirror: http://mirrors.syringanetworks.net/ubuntu-archive/]

 

E: Some index files failed to download. They have been ignored, or old ones used instead.

 

I can categorically state it's not the docker that's broken, Failing to fetch the mirror is something local to you.  Don't forget I installed SABnzbd for the first time less that two hours ago.  My install found the mirrors pulling exactly the same docker file. 

 

EDIT: If you look the mirrors I pulled from and the ones you pulled from are different.  We have no control over the mirrors for Ubuntu....

Link to comment

"Failing to fetch the mirror is something local to you."

 

But you are calling to a different place than I am.  Is the call not coded somewhere as to where to go look?  If it is, then I surely got a different file than you did as it is looking in another place. 

 

So just to be sure...My container came from...  https://hub.docker.com/r/linuxserver/sabnzbd/

 

Wait...Unless you mean LOCAL to me like to looks at the closest repository to my actual location via Internet IP and that repository could be wrong.

Link to comment

"Failing to fetch the mirror is something local to you."

 

But you are calling to a different place than I am.  Is the call not coded somewhere as to where to go look?  If it is, then I surely got a different file than you did as it is looking in another place. 

 

So just to be sure...My container came from...  https://hub.docker.com/r/linuxserver/sabnzbd/

Try temporarily changing your DNS server to 8.8.8.8

 

Link to comment

"Failing to fetch the mirror is something local to you."

 

But you are calling to a different place than I am.  Is the call not coded somewhere as to where to go look?  If it is, then I surely got a different file than you did as it is looking in another place. 

 

So just to be sure...My container came from...  https://hub.docker.com/r/linuxserver/sabnzbd/

 

OK, we pulled the same container, I get that.  But the docker then calls for the Ubuntu mirrors and for some reason, DNS, iffy internet connection, yours isn't connecting at the moment.  We have zero control over that.

 

You're considering all possibilities apart from that it is something local to you....

 

Our docker container is almost an automated install if you like.  It pulls data in from elsewhere, for some reason, YOUR install isn't connecting to the mirrors.  I'm sorry, but look at the evidence. 

 

We (linuxserver.io) are a group from across Europe and America and we tested these containers for you both yesterday and today and we've discussed it in our dev chatroom.  We all pulled the same containers (SABnzbd and Sonarr) and we're all hitting the mirrors.  You are trying and aren't, but we're all pulling the same initial data.  We really have looked into this for you.

 

I'm sure that at some point yours will hook in the meantime there's nothing I can do to help other than advise you to be patient.

 

Hope that helps clear stuff up a bit.

Link to comment

Hi...Ok, just did the DNS change and that and something different took place but I still did not make the upgrade.  But got closer. ;)

 

-----------------------------------
GID/UID
-----------------------------------
User uid:    99
User gid:    100
-----------------------------------

*** Running /etc/my_init.d/20_apt_update.sh...
Hit http://ppa.launchpad.net trusty InRelease
Ign http://mirrors.tripadvisor.com/ubuntu/ trusty InRelease
Get:1 http://mirrors.tripadvisor.com/ubuntu/ trusty-security InRelease [64.4 kB]
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Get:2 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates InRelease [64.4 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty Release.gpg
Get:3 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main Sources [127 kB]
Get:4 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/restricted Sources [3,920 B]
Get:5 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/universe Sources [36.5 kB]
Get:6 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/multiverse Sources [2,165 B]
Get:7 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main amd64 Packages [477 kB]

-----------------------------------
GID/UID
-----------------------------------
User uid:    99
User gid:    100
-----------------------------------

Hit http://ppa.launchpad.net trusty InRelease
Ign http://mirrors.tripadvisor.com/ubuntu/ trusty InRelease
Get:1 http://mirrors.tripadvisor.com/ubuntu/ trusty-security InRelease [64.4 kB]
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Get:2 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates InRelease [64.4 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty Release.gpg
Get:3 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main Sources [127 kB]
Get:4 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/restricted Sources [3,920 B]
Get:5 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/universe Sources [36.5 kB]
Get:6 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/multiverse Sources [2,165 B]
Get:7 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main amd64 Packages [477 kB]
Get:8 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/restricted amd64 Packages [20.2 kB]
Get:9 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/universe amd64 Packages [156 kB]
Get:10 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/multiverse amd64 Packages [4,647 B]
Get:11 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/main Sources [311 kB]
Get:12 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/restricted Sources [5,219 B]
Get:13 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/universe Sources [181 kB]
Get:14 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/multiverse Sources [5,111 B]
Get:15 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/main amd64 Packages [836 kB]
Get:16 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/restricted amd64 Packages [23.4 kB]
Get:17 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/universe amd64 Packages [427 kB]
Get:18 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/multiverse amd64 Packages [14.1 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty Release
Get:19 http://mirrors.tripadvisor.com/ubuntu/ trusty/main Sources [1,335 kB]
Get:20 http://mirrors.tripadvisor.com/ubuntu/ trusty/restricted Sources [5,335 B]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty/universe Sources
Get:21 http://mirrors.tripadvisor.com/ubuntu/ trusty/multiverse Sources [211 kB]
Get:22 http://mirrors.tripadvisor.com/ubuntu/ trusty/restricted amd64 Packages [16.0 kB]
Get:23 http://mirrors.tripadvisor.com/ubuntu/ trusty/universe amd64 Packages [7,589 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty/main amd64 Packages
Get:24 http://mirrors.tripadvisor.com/ubuntu/ trusty/multiverse amd64 Packages [132 kB]
Err http://mirrors.tripadvisor.com/ubuntu/ trusty/main amd64 Packages
  404  Not Found [Mirror: http://mirrors.tripadvisor.com/ubuntu/]
Fetched 4,248 kB in 2min 15s (31.3 kB/s)
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/10_add_user_abc.sh...
*** Running /etc/my_init.d/20_apt_update.sh...
W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/main/binary-amd64/Packages  404  Not Found [Mirror: http://mirrors.tripadvisor.com/ubuntu/]

E: Some index files failed to download. They have been ignored, or old ones used instead.
*** Running /etc/my_init.d/30_set_config.sh...
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 42
Dec  7 18:20:22 24ae7fef105b syslog-ng[50]: syslog-ng starting up; version='3.5.3'
2015-12-07 18:20:23,640::INFO::[sabnzbdplus:1260] --------------------------------
2015-12-07 18:20:23,640::INFO::[sabnzbdplus:1261] sabnzbdplus-0.8.0Beta1 (rev=1ba588f530642cb2b804b58a48c5260ed7cd473e (not committed))

Link to comment

Hi...Ok, just did the DNS change and that and something different took place but I still did not make the upgrade.  But got closer. ;)

 

-----------------------------------
GID/UID
-----------------------------------
User uid:    99
User gid:    100
-----------------------------------

*** Running /etc/my_init.d/20_apt_update.sh...
Hit http://ppa.launchpad.net trusty InRelease
Ign http://mirrors.tripadvisor.com/ubuntu/ trusty InRelease
Get:1 http://mirrors.tripadvisor.com/ubuntu/ trusty-security InRelease [64.4 kB]
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Get:2 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates InRelease [64.4 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty Release.gpg
Get:3 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main Sources [127 kB]
Get:4 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/restricted Sources [3,920 B]
Get:5 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/universe Sources [36.5 kB]
Get:6 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/multiverse Sources [2,165 B]
Get:7 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main amd64 Packages [477 kB]

-----------------------------------
GID/UID
-----------------------------------
User uid:    99
User gid:    100
-----------------------------------

Hit http://ppa.launchpad.net trusty InRelease
Ign http://mirrors.tripadvisor.com/ubuntu/ trusty InRelease
Get:1 http://mirrors.tripadvisor.com/ubuntu/ trusty-security InRelease [64.4 kB]
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Get:2 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates InRelease [64.4 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty Release.gpg
Get:3 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main Sources [127 kB]
Get:4 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/restricted Sources [3,920 B]
Get:5 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/universe Sources [36.5 kB]
Get:6 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/multiverse Sources [2,165 B]
Get:7 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main amd64 Packages [477 kB]
Get:8 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/restricted amd64 Packages [20.2 kB]
Get:9 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/universe amd64 Packages [156 kB]
Get:10 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/multiverse amd64 Packages [4,647 B]
Get:11 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/main Sources [311 kB]
Get:12 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/restricted Sources [5,219 B]
Get:13 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/universe Sources [181 kB]
Get:14 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/multiverse Sources [5,111 B]
Get:15 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/main amd64 Packages [836 kB]
Get:16 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/restricted amd64 Packages [23.4 kB]
Get:17 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/universe amd64 Packages [427 kB]
Get:18 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/multiverse amd64 Packages [14.1 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty Release
Get:19 http://mirrors.tripadvisor.com/ubuntu/ trusty/main Sources [1,335 kB]
Get:20 http://mirrors.tripadvisor.com/ubuntu/ trusty/restricted Sources [5,335 B]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty/universe Sources
Get:21 http://mirrors.tripadvisor.com/ubuntu/ trusty/multiverse Sources [211 kB]
Get:22 http://mirrors.tripadvisor.com/ubuntu/ trusty/restricted amd64 Packages [16.0 kB]
Get:23 http://mirrors.tripadvisor.com/ubuntu/ trusty/universe amd64 Packages [7,589 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty/main amd64 Packages
Get:24 http://mirrors.tripadvisor.com/ubuntu/ trusty/multiverse amd64 Packages [132 kB]
Err http://mirrors.tripadvisor.com/ubuntu/ trusty/main amd64 Packages
  404  Not Found [Mirror: http://mirrors.tripadvisor.com/ubuntu/]
Fetched 4,248 kB in 2min 15s (31.3 kB/s)
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/10_add_user_abc.sh...
*** Running /etc/my_init.d/20_apt_update.sh...
W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/main/binary-amd64/Packages  404  Not Found [Mirror: http://mirrors.tripadvisor.com/ubuntu/]

E: Some index files failed to download. They have been ignored, or old ones used instead.
*** Running /etc/my_init.d/30_set_config.sh...
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 42
Dec  7 18:20:22 24ae7fef105b syslog-ng[50]: syslog-ng starting up; version='3.5.3'
2015-12-07 18:20:23,640::INFO::[sabnzbdplus:1260] --------------------------------
2015-12-07 18:20:23,640::INFO::[sabnzbdplus:1261] sabnzbdplus-0.8.0Beta1 (rev=1ba588f530642cb2b804b58a48c5260ed7cd473e (not committed))

Yep, there is something gone on with the mirror that you are trying to pull from.  People get different mirrors assigned to them  based on their physical location.  Even though you are installing from the same place (https://hub.docker.com/r/linuxserver/sabnzbd/), the mirrors attempt to get a server that is closest to you.  The one that was assigned to you is having issues, if you try again in a few hours you should get a new mirror OR that mirror will have resolved its issues.

Link to comment

Hi...Ok, just did the DNS change and that and something different took place but I still did not make the upgrade.  But got closer. ;)

 

-----------------------------------
GID/UID
-----------------------------------
User uid:    99
User gid:    100
-----------------------------------

*** Running /etc/my_init.d/20_apt_update.sh...
Hit http://ppa.launchpad.net trusty InRelease
Ign http://mirrors.tripadvisor.com/ubuntu/ trusty InRelease
Get:1 http://mirrors.tripadvisor.com/ubuntu/ trusty-security InRelease [64.4 kB]
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Get:2 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates InRelease [64.4 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty Release.gpg
Get:3 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main Sources [127 kB]
Get:4 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/restricted Sources [3,920 B]
Get:5 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/universe Sources [36.5 kB]
Get:6 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/multiverse Sources [2,165 B]
Get:7 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main amd64 Packages [477 kB]

-----------------------------------
GID/UID
-----------------------------------
User uid:    99
User gid:    100
-----------------------------------

Hit http://ppa.launchpad.net trusty InRelease
Ign http://mirrors.tripadvisor.com/ubuntu/ trusty InRelease
Get:1 http://mirrors.tripadvisor.com/ubuntu/ trusty-security InRelease [64.4 kB]
Hit http://ppa.launchpad.net trusty/main amd64 Packages
Get:2 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates InRelease [64.4 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty Release.gpg
Get:3 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main Sources [127 kB]
Get:4 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/restricted Sources [3,920 B]
Get:5 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/universe Sources [36.5 kB]
Get:6 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/multiverse Sources [2,165 B]
Get:7 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/main amd64 Packages [477 kB]
Get:8 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/restricted amd64 Packages [20.2 kB]
Get:9 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/universe amd64 Packages [156 kB]
Get:10 http://mirrors.tripadvisor.com/ubuntu/ trusty-security/multiverse amd64 Packages [4,647 B]
Get:11 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/main Sources [311 kB]
Get:12 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/restricted Sources [5,219 B]
Get:13 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/universe Sources [181 kB]
Get:14 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/multiverse Sources [5,111 B]
Get:15 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/main amd64 Packages [836 kB]
Get:16 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/restricted amd64 Packages [23.4 kB]
Get:17 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/universe amd64 Packages [427 kB]
Get:18 http://mirrors.tripadvisor.com/ubuntu/ trusty-updates/multiverse amd64 Packages [14.1 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty Release
Get:19 http://mirrors.tripadvisor.com/ubuntu/ trusty/main Sources [1,335 kB]
Get:20 http://mirrors.tripadvisor.com/ubuntu/ trusty/restricted Sources [5,335 B]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty/universe Sources
Get:21 http://mirrors.tripadvisor.com/ubuntu/ trusty/multiverse Sources [211 kB]
Get:22 http://mirrors.tripadvisor.com/ubuntu/ trusty/restricted amd64 Packages [16.0 kB]
Get:23 http://mirrors.tripadvisor.com/ubuntu/ trusty/universe amd64 Packages [7,589 kB]
Hit http://mirrors.tripadvisor.com/ubuntu/ trusty/main amd64 Packages
Get:24 http://mirrors.tripadvisor.com/ubuntu/ trusty/multiverse amd64 Packages [132 kB]
Err http://mirrors.tripadvisor.com/ubuntu/ trusty/main amd64 Packages
  404  Not Found [Mirror: http://mirrors.tripadvisor.com/ubuntu/]
Fetched 4,248 kB in 2min 15s (31.3 kB/s)
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/10_add_user_abc.sh...
*** Running /etc/my_init.d/20_apt_update.sh...
W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty/main/binary-amd64/Packages  404  Not Found [Mirror: http://mirrors.tripadvisor.com/ubuntu/]

E: Some index files failed to download. They have been ignored, or old ones used instead.
*** Running /etc/my_init.d/30_set_config.sh...
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 42
Dec  7 18:20:22 24ae7fef105b syslog-ng[50]: syslog-ng starting up; version='3.5.3'
2015-12-07 18:20:23,640::INFO::[sabnzbdplus:1260] --------------------------------
2015-12-07 18:20:23,640::INFO::[sabnzbdplus:1261] sabnzbdplus-0.8.0Beta1 (rev=1ba588f530642cb2b804b58a48c5260ed7cd473e (not committed))

 

That proves the problem is with your connection, now just wait, mirrors go up and down.

Link to comment

"OK, we pulled the same container, I get that. "

 

That was all I was looking to make sure.  I was looking to see if there was a difference somewhere.  Maybe you did call a different container or something. I was looking for a difference. 

 

It is great you all work on these for us.  It is outstanding to say the least.  The issue that things are not always equal and most of us who are using such tools only do so for we do not know how to work with the OS directly.  Docker, as you know much better than I, was originally made for a sandbox for testing. Here it is being used as an install tool to make it easy for users of UnRAID, or other such systems, where people need installers.

 

I have spent the last 3 days working on two installs.  Two.  The documentation for UnRAID and using docker is very sparse. Mapping information is not clear and was most of my issue as some things worked, and some did not. Then you have the issue of so many different containers for the same program and which one to actually use. I went with Linuxserver.io ones as they seemed to be supported. (And are, so thanks.)

 

All in all when I happened to notice I had not received the most current versions I went out seeking how to upgrade as these were from a Docker file.  Again, no information is available.  More research looking for answers such as can you use the automatic updater built into something like Sonorr or do you have to let Docker take care of it?  Then that gets more confusing as when you look at Dockers tab you see "Up-to-date". But it is not stated anywhere that it is not referring to the program installed, but the container.

 

So then I find out you just need to just restart the application to get an update. Well, who would think restarting something would also upgrade it without you telling it to do so or it at least asking you?  I would not have thought that. (IE, what if the new version actually has issues that are being reported and you do not want to upgrade to that version.)  So ok, I do that and then find it may or may not work based on the internet. Someone as a normal user, like me, would have no idea what is happening. All you know at this time is you can not get the program when trying to call it up on your browser. (No idea it is trying to look for an upgrade and thus has not even loaded yet. And if it finds it, it needs to download and install. By that time you are clicking RESTART again.)  Oh, wonderful.  :)

 

Anyway, thanks for all the help on this for I clearly do not have any clue on Docker and in turn the containers or the updates. Then when you run into the issues mentioned above, it can, and does, get someone totally lost. Well, it has been a long three days to get something running that I have run for years on a Windows machine. :)

 

Thank you again for looking into the issues I had (have) and to help get me running. I do thank you for how you maintain this stuff.

 

(Someone needs to write a..."Hey you!  Yes You. Here is what you should know about using Docker before you freak out."  :)

Link to comment

Docker, as you know much better than I, was originally made for a sandbox for testing. Here it is being used as an install tool to make it easy for users of UnRAID, or other such systems, where people need installers.

Docker is being used in unRaid how it is intended.  As an app platform.  Docker authors set it up once, and it becomes portable to any system running docker on any OS.

 

Where linuxserver's implementation of their containers differs from the docker ideal is that of the auto-updating.  Different opinions on that score.

 

From docker's homepage:

 

Docker containers wrap up a piece of software in a complete filesystem that contains everything it needs to run: code, runtime, system tools, system libraries – anything you can install on a server. This guarantees that it will always run the same, regardless of the environment it is running in.
  And that is also the same reason why auto updates go against the ideal of docker.  (But are not necessarily a bad thing depending upon the audience and environment)
Link to comment

Hey....Does it only run an UPDATE when you tell it to restart a given application? Or will it also look for new versions when you reboot the server?

 

(I ask for when we move the coach like we will tomorrow, I shut the server down to protect the drives.)

 

Thanks

 

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.

Link to comment

 

(Someone needs to write a..."Hey you!  Yes You. Here is what you should know about using Docker before you freak out."  :)

 

like this you mean ?

 

http://lime-technology.com/forum/index.php?topic=37732.0

 

Yep, I did read that.  But it still does not help with things like upgrades and that Up-To-Date does not really mean that if taking about what you installed etc.  A lot of the thread was issues people still had with mappings and where to put things right down to be sure to use the cache and set it to use that only. I did read the thread, and still, sorry to say, had mapping issues and where and where not I should put things.

Link to comment

Hey....Does it only run an UPDATE when you tell it to restart a given application? Or will it also look for new versions when you reboot the server?

 

(I ask for when we move the coach like we will tomorrow, I shut the server down to protect the drives.)

 

Thanks

 

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.

Link to comment

 

(Someone needs to write a..."Hey you!  Yes You. Here is what you should know about using Docker before you freak out."  :)

 

like this you mean ?

 

http://lime-technology.com/forum/index.php?topic=37732.0

 

Yep, I did read that.  But it still does not help with things like upgrades and that Up-To-Date does not really mean that if taking about what you installed etc.  A lot of the thread was issues people still had with mappings and where to put things right down to be sure to use the cache and set it to use that only. I did read the thread, and still, sorry to say, had mapping issues and where and where not I should put things.

 

 

I'm really not sure how much easier we can make it for you, we (the members of this forum in general) have given you a great deal of assistance on matters of mapping etc.

 

You must be at least reasonably familar with the notions of paths having used these apps on windoze, the external side of a mapping goes to the downloads folder for whatever apps share it, the internal which you don't edit goes to /downloads.

 

both dockers are as far as they are concerned, all the files are in /downloads...

 

i really don't know how to make this easier to understand.

Link to comment

Hey....Does it only run an UPDATE when you tell it to restart a given application? Or will it also look for new versions when you reboot the server?

 

(I ask for when we move the coach like we will tomorrow, I shut the server down to protect the drives.)

 

Thanks

 

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.
Link to comment

Hey....Does it only run an UPDATE when you tell it to restart a given application? Or will it also look for new versions when you reboot the server?

 

(I ask for when we move the coach like we will tomorrow, I shut the server down to protect the drives.)

 

Thanks

 

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.

 

 

*takes squid outside and beats him with a ham hock

Link to comment

Hey....Does it only run an UPDATE when you tell it to restart a given application? Or will it also look for new versions when you reboot the server?

 

(I ask for when we move the coach like we will tomorrow, I shut the server down to protect the drives.)

 

Thanks

 

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.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.