-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on notification settings #6
Comments
Which platform are you running the image on? Crashing without any messages makes me think of a recent Docker bug that could be causing the crash. |
I'm running it on CentOS x64. |
I've tried running it on Docker version 1.12.3, build 6b644ec and the problem remains. |
OK, I'll try and reproduce tonight. |
I'm able to reproduce the issue. There doesn't appear to be any messages in the log or console. I'll try and dig deeper and try and find out what is causing the exit. |
@ressu Any progress on this? |
I'm having a hard time getting this resolved, it feels a lot like an musl compatibility issue. I'm currently trying to narrow down what is actually causing the crash and working backwards from there |
This release fixes SickGear#6
The fixed builds should now be up. Took me a bit longer to get around to fixing this than I expected.. The only solution I could find was to switch away from the Alpine based image to Debian based image. |
Yes, this solved the problem nicely. Thanks! |
@ressu this can be fixed by setting the threading stack size in SickGear. Thus we can continue to use Alpine as the base. These are the refs to the root cause of the issue: python-pillow/Pillow#1935 |
Cool, I personally prefer Alpine over Debian for the Docker image. Pull requests are welcome, I'm not sure when I'm able to revert PR #8 and test with the new threading stack sizes. |
So I've spoken with @JackDandy and we're working on testing a config directive for specifying the default thread stack size. That way we can revert to an Alpine based docker image in master, and just update the config template to specify the stack size to something large enough to keep it working. I haven't yet managed to test the PR over on kulta regarding this new config setting though. |
Thanks for looking into the fix, however, shouldn't this one still be open ? Took me a little to dig it up is all |
@timm088 I basically investigated and resolved the issue entirely independently before realising it was fixed on master, because there wasn't an open issue :( |
Ok thanks. Would be great if that pr could be linked here, so I can just pulled it myself? |
Checkout the master branch
Or view my fork and the dev branch
|
Last commit on master was
Problem still exists for Alpine docker images on current master branch No problems if it isn't merged yet, I manually configured notifications via config.ini (which for me is mounted into the container each time) |
I can't find the commit you're referring to... This is the latest commit on the master branch: |
Sorry, i'm referring to the master branch of Sickgear itself, not the dockerfile i.e., you said its fixed on master? You mean changed to debian, not actually fixed (i.e, threading stack size fixed) |
If you just want to change the SickGear version to fix this issue, you can use this commit from the current hotfix branch: 70edd5462fca9ebdfc4ffa6caef7708219e79704 Then set the stack_size = 327680 under General in config.ini |
Hotfix branch? |
Did you actually find the commit I referred to? |
You do realise there is no hotfix branch right? Guessing hotfix branch is private? You mean this commit? SickGear/SickGear@70edd54 |
https://git.kulta.us/SickGear/SickGear/src/hotfix/0.12.26 That's the right commit yes. |
Merged into master on github now for anyone else that might come across this. |
Whenever I try to access the notification settings the docker container crashes without any error messages. I'm running the container with your example command but with modified values for paths, uid and gid
The text was updated successfully, but these errors were encountered: