Jump to content

Docker vs Plugin


hernandito

Recommended Posts

Not going to run into dependency issues, dockers are much easier for people to maintain and update, so you're more likely to get current versions.  For things like CouchPotato & Sonarr they really are the way forward in my opinion.

 

Why don't you run your plugins as normal and try setting the dockers up, don't try and do it all in one go and then see.

Link to comment

When the last plugin developer gives up you will have to go to docker anyway.

 

Sadly Docker has the same problem.  Take me for example.. I'm kinda here, but not a lot of time to support/update my dockers.

But you're not the last docker developer. For the apps he's talking about, which are better implemented as dockers anyway, I think PhAzE is all that's left. Maybe overbyrn but he's not very active recently. Some things need to be plugins (or built-in), such as Unassigned Devices. Some don't and shouldn't be going forward.
Link to comment

Another reason. If you have an issue with unRAID itself, the first step in debugging is SAFE mode. Maybe a docker could cause an issue beyond itself but not likely, since that's sort of the point. And you can stop dockers individually. You may be able to turn off a plugin, but that doesn't undo the damage that it might have already done during installation.

Link to comment

When the last plugin developer gives up you will have to go to docker anyway.

 

Sadly Docker has the same problem.  Take me for example.. I'm kinda here, but not a lot of time to support/update my dockers.

 

but you could share rights on your github and someone who knows apache/nginx etc could easily step in.

 

plugins are little more esoteric.

Link to comment

When the last plugin developer gives up you will have to go to docker anyway.

 

Sadly Docker has the same problem.  Take me for example.. I'm kinda here, but not a lot of time to support/update my dockers.

 

but you could share rights on your github and someone who knows apache/nginx etc could easily step in.

 

plugins are little more esoteric.

 

Very true.  Dockerfile's are a lot easier to compose. Also, I'd be happy to give out rights to any of the other docker dev's here if they want it ;)

Link to comment

When the last plugin developer gives up you will have to go to docker anyway.

 

Sadly Docker has the same problem.  Take me for example.. I'm kinda here, but not a lot of time to support/update my dockers.

 

but you could share rights on your github and someone who knows apache/nginx etc could easily step in.

 

plugins are little more esoteric.

 

Very true.  Dockerfile's are a lot easier to compose. Also, I'd be happy to give out rights to any of the other docker dev's here if they want it ;)

 

I remember you offering a while back, alas I don't think I'm up to the task, but Apache was pretty much the first docker container I really got my teeth into, so much so I modified yours!  ;D

Link to comment

When the last plugin developer gives up you will have to go to docker anyway.

 

Sadly Docker has the same problem.  Take me for example.. I'm kinda here, but not a lot of time to support/update my dockers.

True, but there is one big difference.

 

As unRaid evolves (new Kernels, etc) plugins may have to be re-written to work on the new system.  A docker container does not have that problem.  A container that worked on 6.0b10 will still work on 6.0 Final, and and will still work on unRaid 7.0 etc.

Link to comment

OK... a follow up...

 

Is there a reason why the three big ones Sab, SB, and CP are separate Dockers and not on a single combined docker? Is there an advantage/disadvantage to this? This question probably goes to the root basics of Docker.

 

I know some may use Sickrage  over SB, Sonarr or NZBGet over Sab... and I can see why a combo Docker would not be practical for people who have varied preferences.

 

Also, Binhex has template repos for them, as well as gfjardim.... are differences or recommendations which ones to use?

 

 

Link to comment

I was dreading this.... I will give them a try... slowly... hopefully I can reuse all the configs and settings from existing install...

 

Thanks...

 

What I did was install my dockers and manually copy across my config bit by bit, there are some bits you can't use so copying across .ini files won't work.  For instance if you set your download directory in a plugin to /mnt/cache/downloads then you can't use that in a docker, it's more likely going to end up as /downloads

 

From personal experience I can guarantee copying stuff blindly will end in tears...

 

Here are my docker mappings for nzbget, couchpotato & sonarr.  Note how downloads is mapped in each container and always has the same path.  Not "getting" that concept is a common mistake when starting out.  But once it clicks it's straightforward. 

 

Personally I wouldn't go back to plugins from my dockers.

 

Db6JTou.jpg

 

HBg52gy.jpg

 

I9Dxne7.jpg

 

Let us know if you need a hand mate.

Link to comment

OK... a follow up...

 

Is there a reason why the three big ones Sab, SB, and CP are separate Dockers and not on a single combined docker? Is there an advantage/disadvantage to this? This question probably goes to the root basics of Docker.

 

I know some may use Sickrage  over SB, Sonarr or NZBGet over Sab... and I can see why a combo Docker would not be practical for people who have varied preferences.

 

Also, Binhex has template repos for them, as well as gfjardim.... are differences or recommendations which ones to use?

 

My opinion is because there are few different ways to run it.  Some people like Sonarr>SB or NZBGet>SAB and vice versa.  So everyones setup may be a little bit different.

 

Also, i think, the point of dockers is to keep everything separate as its own "service".  That way if your break one, it doesn't break the other.

 

As far as Binhex vs gfjardim. Binhex runs his on an Arch linux base image and gfjardim (and most of us) run on a phusion (debian) base image.  Its a preference on what you think is better.  What you have to be concerned about is with how docker works. If you have all of your dockers with the same base image, it will take less resources than running multiple base images.

Link to comment

OK... a follow up...

 

Is there a reason why the three big ones Sab, SB, and CP are separate Dockers and not on a single combined docker? Is there an advantage/disadvantage to this? This question probably goes to the root basics of Docker.

 

I know some may use Sickrage  over SB, Sonarr or NZBGet over Sab... and I can see why a combo Docker would not be practical for people who have varied preferences.

 

Also, Binhex has template repos for them, as well as gfjardim.... are differences or recommendations which ones to use?

 

Well, it's not recommended to update apps within a docker container, rather the docker container itself gets updated.  So packaging apps together has some distinct disadvantages.

 

Binhex uses Arch Linux, gfjardim uses Debian, you can mix and match, but I personally use gfjardim generally, purely because I'm  a Debian kind of guy... I do use Binhex's Deluge VPN container though and very good it is too.

Link to comment

OK... a follow up...

 

Is there a reason why the three big ones Sab, SB, and CP are separate Dockers and not on a single combined docker? Is there an advantage/disadvantage to this? This question probably goes to the root basics of Docker.

You're right -> this is all about the basics / fundamentals of Docker.  The whole key here is sandboxing.  If Sab happens to crash, then its not going to affect CP, won't affect SB as long as they are in separate containers.  If they were all in the same container, then one could affect the other.

 

Also, it is also possible that if all three were the in the same container, then an update to one of them could impact functionality to the other 2.  Separate containers it just won't happen.

 

There is no extra overhead (or extremely minimal) by having them separate.  All communication between them would still happen either through the API or watched folders.

 

As far as the differences between gfjardim's and binhex's, I believe the fundamental difference is the base OS that they run.  gfjardim I think uses Phusion and binhex is using Arch.  Just a different approach to accomplish the same thing.  I would however choose to install either the ones from gfjardim or the ones from binhex and not mix and match.  There isn't an issue by doing so however, but when possible I would think a matched set is prefereable.

Link to comment

As far as the differences between gfjardim's and binhex's, I believe the fundamental difference is the base OS that they run.  gfjardim I think uses Phusion and binhex is using Arch.  Just a different approach to accomplish the same thing.  I would however choose to install either the ones from gfjardim or the ones from binhex and not mix and match.  There isn't an issue by doing so however, but when possible I would think a matched set is prefereable.

 

Matching base image as far as possible is good for space utilisation if nothing else.

Link to comment

 

What I did was install my dockers and manually copy across my config bit by bit, there are some bits you can't use so copying across .ini files won't work.  For instance if you set your download directory in a plugin to /mnt/cache/downloads then you can't use that in a docker, it's more likely going to end up as /downloads

 

From personal experience I can guarantee copying stuff blindly will end in tears...

 

 

Tears indeed... The main stuff I do not want to re-do, is like in Sickbeard, to re-add all my shows... and the settings... although settings is not that bad to redo.

 

In CP, the same thing, adding all my wanted movies.

 

Any ideas?

 

Thank you.

Link to comment

 

What I did was install my dockers and manually copy across my config bit by bit, there are some bits you can't use so copying across .ini files won't work.  For instance if you set your download directory in a plugin to /mnt/cache/downloads then you can't use that in a docker, it's more likely going to end up as /downloads

 

From personal experience I can guarantee copying stuff blindly will end in tears...

 

 

Tears indeed... The main stuff I do not want to re-do, is like in Sickbeard, to re-add all my shows... and the settings... although settings is not that bad to redo.

 

In CP, the same thing, adding all my wanted movies.

 

Any ideas?

 

Thank you.

 

99% sure when I did this. I shutdown SB/SAB/CP (so the db files were clean) and copied their config folders/files so that the structure was the same into the correct appdata folder and it all worked.

Link to comment

 

What I did was install my dockers and manually copy across my config bit by bit, there are some bits you can't use so copying across .ini files won't work.  For instance if you set your download directory in a plugin to /mnt/cache/downloads then you can't use that in a docker, it's more likely going to end up as /downloads

 

From personal experience I can guarantee copying stuff blindly will end in tears...

 

 

Tears indeed... The main stuff I do not want to re-do, is like in Sickbeard, to re-add all my shows... and the settings... although settings is not that bad to redo.

 

In CP, the same thing, adding all my wanted movies.

 

Any ideas?

 

Thank you.

 

99% sure when I did this. I shutdown SB/SAB/CP (so the db files were clean) and copied their config folders/files so that the structure was the same into the correct appdata folder and it all worked.

 

Nothing to lose by trying I suppose, whenever I do anything there's always a fair amount of PEBKAC.

Link to comment

 

What I did was install my dockers and manually copy across my config bit by bit, there are some bits you can't use so copying across .ini files won't work.  For instance if you set your download directory in a plugin to /mnt/cache/downloads then you can't use that in a docker, it's more likely going to end up as /downloads

 

From personal experience I can guarantee copying stuff blindly will end in tears...

 

 

Tears indeed... The main stuff I do not want to re-do, is like in Sickbeard, to re-add all my shows... and the settings... although settings is not that bad to redo.

 

In CP, the same thing, adding all my wanted movies.

 

Any ideas?

 

Thank you.

 

99% sure when I did this. I shutdown SB/SAB/CP (so the db files were clean) and copied their config folders/files so that the structure was the same into the correct appdata folder and it all worked.

 

CP can be a bitch about db versions though.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...