-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ocrmypdf-alpine not working #426
Comments
@AmirthaKrishnan Please use "New issue" in Github to open a new issue, and please refrain from commenting on issues that are unrelated to the problem you are having. ocrmypdf-alpine is broken at the moment since the Alpine qpdf has not upgraded to 9.0.0. I suggest using |
Thanks for the reply @jbarlow83 |
9.0.1-r0 is in edge, so it should be possible to upgrade the image. |
I think it's fine now. |
Just pulled the image from docker hub, still getting the same error (trying via the webinterface): Traceback (most recent call last): |
After building the image by myself (libqpdf.so.26 is in edge, so it should work...) I am getting this error from the web-frontend: Traceback (most recent call last): Ok, it is the right version now, but still does not work. |
from the pikepdf docs
So, this is probably the problem. |
@kykim I wish it were that simple. From the build logs pip is already doing the right thing and building pikepdf from source. I think the issue is that libqpdf is being compiled without C++11 and pikepdf requires C++11. On glibc this doesn't matter but it does for Alpine's musl libc. |
I am still having an issue with the latest version, 8.2.1 works fine `Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Hello, the :latest version is not working, getting also the pikepdf import error. Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): v9.0.3 is working fine |
I do apologize for the frustrations people have had with ocrmypdf-alpine these past few months. Is there anyone who would object to me killing off ocrmypdf-alpine in favor of the Ubuntu based jbarlow83/ocrmypdf image? @mawi12345 - want to make sure you're part of this discussion since you contributed the alpine image.
I'd rather have a smaller set of installations that work reliably, and the Ubuntu image is quite stable because Travis CI implicitly tests it. Alternately, is someone willing to volunteer to maintain ocrmypdf-alpine? |
It is fine for me. I also prefer a stable solution over a set of choices which may work or may not work. |
I've made some improvements to the Ubuntu version and removed ocrmypdf-alpine. |
@jbarlow83: The ubuntu image has improved a lot since my first alpine version. I prefer the simpler way to only support one image. Drop the |
@jbarlow83 pls help me out.!"
I cant able to pull the latest version of ocrmypdf.
If i use this command - docker pull jbarlow83/ocrmypdf-alpine am in the version of 8.2.2.post10+g6e49bb3.d20190403
How to get the latest version of ocrmypdf in docker.?
Thanks
Originally posted by @AmirthaKrishnan in #419 (comment)
The text was updated successfully, but these errors were encountered: