search

theotherp / nzbhydra2

Usenet meta search
Other
1.27k stars 76 forks source link

Docker detection confirmation #80

Closed mrhotio closed 6 years ago

mrhotio commented 6 years ago

Running NZBHydra2 inside suitarr docker container, docker seems to be detected OK.

hydra

theotherp commented 6 years ago

Thanks for the feedback!

Am 21.01.2018 4:52 nachm. schrieb "hotio" notifications@github.com:

Running NZBHydra2 inside suitarr docker container, docker seems to be detected OK.

[image: hydra] https://user-images.githubusercontent.com/26902309/35195941-691b4b0e-fecb-11e7-8726-e50da5e5750b.png

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/80, or mute the thread https://github.com/notifications/unsubscribe-auth/ANtAed_Y_hiIjwMr3-ZD3ylkQry4_UVWks5tM11EgaJpZM4Rl3Jk .

Elfman72 commented 6 years ago

So can I ask why this is the preferred method of updating?

I am running this within a Synology Docker and updating the container would require me to rebuild the container. I know I don't have to delete the db or cfg but it is nowhere near as elegant as simply updating from within the app itself.

theotherp commented 6 years ago

I agree. But a) it's "not the docker way" (I was told) but you don't need to care about that and b) see https://github.com/theotherp/nzbhydra2/issues/60#issuecomment-358294742

Because I know that the internal backup is so convenient I still left an option to use it and you're free to do so and ignore the warning.

Am 23.01.2018 05:20 schrieb "Elfman72" notifications@github.com:

So can I ask why this is the preferred method of updating?

I am running this within a Synology Docker and updating the container would require me to rebuilt the container. I know I don't have to delete the db or cfg but it is nowhere near as elegant as simply updating from within the app itself.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/80#issuecomment-359672030, or mute the thread https://github.com/notifications/unsubscribe-auth/ANtAeTBhEsJUlAXwpZua8W8KU2gAWczvks5tNV4FgaJpZM4Rl3Jk .

titocr commented 6 years ago

In this screenshot, I'm being shown different current and latest versions, and it is also telling me "You're up to date!". I do think that 1.1.3 is the latest version available to docker, but that maybe 1.1.4 is available on github?

screen shot 2018-01-23 at 5 56 34 pm

theotherp commented 6 years ago

@titocr What docker?

The update mechanism works independently from docker. It might happen that there's a new release that's displayed but docker is not up to date but that it shows a newer "Latest version" but doesn't allow you to update is rather weird (as in "probably a bug").

titocr commented 6 years ago

Docker version 18.01.0-ce, build 03596f5 -- on ubuntu 17.10

At the time of the screenshot, I had done "docker pull" which brought me up to 1.1.3. About 3hrs after posting this issue, hydra2 got updated (by v2tec/watchtower), so this morning I'm on 1.1.4 and things look all right. So, there's a not-serious little something in there somewhere.

theotherp commented 6 years ago

Hm.. I'll take a further look. Closing this for now as the main issue seems to be solved.