Two Simultaneous Jackett Dockers

[Cpt. Chaz]

Was looking at running two separate instances of jackett docker, one binhex and linuxserver, in hopes to speed up query time. but even with different ports and appdata folders, i can't seem to get both of them working side by side. has anybody ever tried this?

[dukiethecorgi]

I have three instances of linuxserver jackett running - public trackers, private trackers and anime trackers.  Using different appdata folders and ports, everything works fine

[Cpt. Chaz]

you're using the same linux server docker, just 3 different instances, i wonder if that has anything to do with your success? I tried different ports and appdata... at your convenience, would you mind sharing a screenshot of your container configs w/ ports?

[dukiethecorgi]

Here you go!  As you can see, different port # and appdata locations, nothing else needed tweaking

[Cpt. Chaz]

yep, that's exactly what i did too, using bin-hex's container. 

 

however when both containers are on, only one works, the other fails on all indexers. what's curious is trying to open the log for each different container (jackett1 and jackett2), the log window for jackett2 reverts to the same window for jackett1. log also shows

 

Content root path: /usr/lib/jackett/Content

i wonder if that has something to do with my problem? maybe i should just switch containers 🤨

 

EDIT: Nope, that's not it

Edited June 15, 2020 by Cpt. Chaz

[Cpt. Chaz]

I tried installing two new instances of linuxserver's jackett. different appdata and ports, exactly like your screenshots (and also the webui port). In instance 1, i loaded indexer ABC. then when i turn on and open instance 2, it shows indexer ABC already loaded. 

Edited June 15, 2020 by Cpt. Chaz
typo

[dukiethecorgi]

I think I know what's going on.  In my case, each one of the Jackett instances is using a different set of trackers (public trackers, private trackers and anime trackers).  It looks like you are using the same trackers in each instance.  I don't think that will work because your using the same credentials for simultaneous logins