Jump to content
activ

[Support] activ - LazyLibrarian

53 posts in this topic Last Reply

Recommended Posts

Update februari 2018: I no longer have the possibility to keep supporting this docker. If anyone wants to take over please feel free, grab my stuff from GitHub and make your own. 

 

 

Overview: Support for Docker image arch-lazylibrarian in the activ repo.

 

Application: LazyLibrarian https://github.com/DobyTang/LazyLibrarian

Docker Hub: https://hub.docker.com/r/activ/arch-lazylibrarian/

GitHub: https://github.com/activ/arch-lazylibrarian

 

Credit: Most of the work was done by Binhex making the arch-base image.

Edited by activ

Share this post


Link to post

fast work :-), couple of things i spotted:-

 

1. i would alter your link to github to point at the application source files, https://github.com/activ/arch-lazylibrarian, most people arent really concerned about the docker xml tbh.

 

2. i see your doing a git clone, whilst this of course works, you might want to consider using AUR (arch user repo) its got pretty much every app under the sun, you can use a package "helper" to make the process of installation pretty easy, take a look here for example of how im doing this for couchpotato:-

 

https://github.com/binhex/arch-couchpotato/blob/master/setup/root/aur.sh 

 

all you would need to do is change line 10 to be the package name, in this case "lazylibrarian-git" and your good to go, the only things you need to identify is where the package gets installed to so you can kick it off in supervisor, you can search AUR for packages here:-

 

https://aur.archlinux.org/packages/?setlang=en

 

i hope this helps.

Share this post


Link to post

Thanks, tips are very welcome.

 

No.1 is done and I'll have a look at number 2 when I get some time.

 

I'm still getting my bearings on Arch, so I'll do some testing with Aur before changing anything.

Share this post


Link to post

I've now also done the switch from git to AUR,the update has been pushed to the docker repo.

Share this post


Link to post

I've now also done the switch from git to AUR,the update has been pushed to the docker repo.

 

cool, one other thing you might want to consider is switching from building images locally to getting dockerhub to do the building, this has the advantage that you keep your build env off your environment, as well as people then being able to see the output of the build on dockerhub, not to mention support for tags too.

 

so you can hook github and dockerhub together, and you then set it to auto trigger a build on any github commits or you can set dockerhub to manual trigger, i would advise the second option as this then gives you control to add in tags in dockerhub. tags are important and allows the users to roll back incase of either a bad build or an issue with the app, i basically tag all my releases with <aur release>-XX where XX is a numeric indicating my build count for that version, e.g. for lazylibrarian the tag for first build would be 736.d66f7e9-1-01, this is a funny one as its a github build number so its a bit more cryptic, but you get the idea :-).

 

just to be clear when under heavy dev i would advise building locally until you are confident enough to push it to github and build using dockerhub, building locally is still faster than building on dockerhub.

Share this post


Link to post

Have you tested deluge native connections? I'm getting an error

Deluge: Connect FAILED
[Errno 111] Connection refusedCheck Deluge HOST and PORT settings

using the same settings that work successfully in sonarr and couchpotato.

Share this post


Link to post

Have you tested deluge native connections? I'm getting an error

Deluge: Connect FAILED
[Errno 111] Connection refusedCheck Deluge HOST and PORT settings

using the same settings that work successfully in sonarr and couchpotato.

 

Hey, I'm not sure what you mean. Are you saying you are trying to have LazyLibrarian connect to the deluge in your other docker?

No, I have not tested that. Don't really see why it would be an issue though.

 

If the deluge is the one with vpn in it, maybe the iptables firewall is the one blocking things (there are several ip ranges involved).

 

If you can give me a better picture of what you are trying to do I'll try and give you some troubleshooting tips.

Share this post


Link to post

I've now also done the switch from git to AUR,the update has been pushed to the docker repo.

 

cool, one other thing you might want to consider is switching from building images locally to getting dockerhub to do the building, this has the advantage that you keep your build env off your environment, as well as people then being able to see the output of the build on dockerhub, not to mention support for tags too.

 

so you can hook github and dockerhub together, and you then set it to auto trigger a build on any github commits or you can set dockerhub to manual trigger, i would advise the second option as this then gives you control to add in tags in dockerhub. tags are important and allows the users to roll back incase of either a bad build or an issue with the app, i basically tag all my releases with <aur release>-XX where XX is a numeric indicating my build count for that version, e.g. for lazylibrarian the tag for first build would be 736.d66f7e9-1-01, this is a funny one as its a github build number so its a bit more cryptic, but you get the idea :-).

 

just to be clear when under heavy dev i would advise building locally until you are confident enough to push it to github and build using dockerhub, building locally is still faster than building on dockerhub.

 

Sounds cool, I'll look into that.

Share this post


Link to post

Have you tested deluge native connections? I'm getting an error

Deluge: Connect FAILED
[Errno 111] Connection refusedCheck Deluge HOST and PORT settings

using the same settings that work successfully in sonarr and couchpotato.

 

Hey, I'm not sure what you mean. Are you saying you are trying to have LazyLibrarian connect to the deluge in your other docker?

No, I have not tested that. Don't really see why it would be an issue though.

 

If the deluge is the one with vpn in it, maybe the iptables firewall is the one blocking things (there are several ip ranges involved).

 

If you can give me a better picture of what you are trying to do I'll try and give you some troubleshooting tips.

You've got it, exactly. I have delugevpn docker happily connected to the sonarr docker on port 8112, and the couchpotato docker on 58846, but neither configuration allows the lazylibrarian docker to connect. In googling, I noticed that headphones just recently got the ability to talk directly to deluge, and I wondered if the migration to lazylibrarian was only half cooked.

Share this post


Link to post

Just had a quick look to see if I could get it to work and you need port 58846 and the username/password from the auth file (I did test with the non vpn version so I could be quick).

 

Share this post


Link to post

Just had a quick look to see if I could get it to work and you need port 58846 and the username/password from the auth file (I did test with the non vpn version so I could be quick).

On a hunch I tried saving the settings and THEN hitting the test deluge button, and what do you know, it works. I ASSumed that the test connection button was there so you could verify it BEFORE you saved the changes, but obviously not.

 

Sorry for being dense.

Share this post


Link to post

Is there an option somewhere to dismiss the warning that blocks access to the bottom right of all the pages?

Running a local updated version.
Push changes to GITHub or 
rollback to Master release 

Share this post


Link to post

Are these git errors to be expected with your implementation? I suspect they are causing the overlay warning I referenced in my previous post.

2016-05-08 12:58:57	INFO	Starting LazyLibrarian web server on http://0.0.0.0:5299/
2016-05-08 12:58:57	INFO	Starting LazyLibrarian on port: 5299
2016-05-08 12:58:57	INFO	[VersionCheck] - You are running an unknown version of lazylibrarian. Run the updater to identify your version
2016-05-08 12:58:57	WARNING	(getCommitDifferenceFromGit) - Could not get commits behind from github. Can happen if you have a local commit not pushed to repo
2016-05-08 12:58:57	INFO	[VersionCheck] - Comparing currently installed version with latest github version
2016-05-08 12:58:57	ERROR	(getCurrentVersion) Couldn't find latest git installed version.
2016-05-08 12:58:57	ERROR	git not found - please ensure git executable is in your PATH
2016-05-08 12:58:57	ERROR	git not found - please ensure git executable is in your PATH
2016-05-08 12:58:57	INFO	Checking database
2016-05-08 12:58:57	INFO	Config file loaded
2016-05-08 12:58:57	INFO	Screen Log set to INFO/WARN/ERROR
2016-05-08 12:58:57	INFO	Log level set to [2]- Log Directory is [/config/lazylibrarian/Logs] - Config level is [2]

Share this post


Link to post

Yes, that's expected. It's caused by now using git for the installation. My first version used git and didn't have this error, but using git in docker is actually not good practice (as noted by Binhex earlier).

 

It's safe to ignore the message as it only prevents updates and doesn't impact anything else.

Share this post


Link to post

Yes, that's expected. It's caused by now using git for the installation. My first version used git and didn't have this error, but using git in docker is actually not good practice (as noted by Binhex earlier).

 

It's safe to ignore the message as it only prevents updates and doesn't impact anything else.

Would it be possible to suppress the message somehow? It interferes with my ability to click on active elements behind it, specifically when trying to navigate a multipage list, or select the last book in said list. I can work around it with careful scrolling, but having the ability to acknowledge it and move on with life would be nice.

Share this post


Link to post

Activ if this docker requires git to do update checks then just remove the line at the end that uninstalls git and you should be good. I only uninstall git to keep the size down that's all.

 

Sent from my SM-G900F using Tapatalk

 

 

Share this post


Link to post

I put the Git package in for now to get rid of the error message. Not a very clean solution, but at least it works.

The update is already pushed, if you update the docker image the error should be gone.

Share this post


Link to post

Hi,

 

I have an issue with LL where I can no longer longer access the webui.

 

This site can’t be reached

 

192.168.1.250 refused to connect.

 

I haven't changed any settings, although I think there may have been an auto-update occur. Regardless, it was working and now it isn't, with no input from me.

 

 

Tried restarting, tried forced update, any suggestions?

 

Share this post


Link to post

Maybe you could remove it and reinstall, then disable auto update.

 

Share this post


Link to post

Hi Activ - Any idea why lazylibrarian's auto-updater dosn't update the application? i've tried forcing update through unraid but have a popup complaining about being 174 commits behind latest...when i hit update within lazylibrarian it says "updating..." but dosnt seem to be doing anything :)

Share this post


Link to post

Did you try updating from within the apppication en restarting the docker after?

Might be the updated fails to restart due to the lack of a normal init system.

Share this post


Link to post

This is what I get whenever I try to update via the app

21-Aug-2016 16:43:28 - INFO    :: MAIN : LazyLibrarian is updating...
21-Aug-2016 16:43:28 - DEBUG   :: MAIN : (RunGit)Trying to execute: "git rev-parse --abbrev-ref HEAD" with shell in /opt/lazylibrarian
21-Aug-2016 16:43:28 - DEBUG   :: MAIN : (RunGit)Git output: [master]
21-Aug-2016 16:43:28 - DEBUG   :: MAIN : (getCurrentGitBranch) Current local branch of repo is [master]
21-Aug-2016 16:43:28 - DEBUG   :: MAIN : (RunGit)Trying to execute: "git stash clear" with shell in /opt/lazylibrarian
21-Aug-2016 16:43:28 - DEBUG   :: MAIN : (RunGit)Git output: []
21-Aug-2016 16:43:28 - DEBUG   :: MAIN : (RunGit)Trying to execute: "git pull origin master" with shell in /opt/lazylibrarian
21-Aug-2016 16:43:28 - DEBUG   :: MAIN : (RunGit)Git output: [fatal: '/tmp/packerbuild-1000/lazylibrarian-git/lazylibrarian-git/LazyLibrarian' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights

Share this post


Link to post

Weird, does LL work normally otherwise?

Is it possible that it cannot connect to the internet?

Share this post


Link to post

Weird, does LL work normally otherwise?

Is it possible that it cannot connect to the internet?

Yes it works normally otherwise

 

Sent from my SM-G920V using Tapatalk

 

 

Share this post


Link to post

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.