-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
Kavita on Alpine can't open PDFs #1507
Comments
Since I'd already pretty much finalized a container image for Kavita on Alpine, I'll share it here. https://gist.github.com/RealStickman/41beffac2e973378ce319ab9d15eeb4c |
I put this as on-hold for myself, but opening it up to the community to help out here. |
See @docnet/issues/7 - it's issue of docnet - they bundle pdfium library compiled not against musl.. So i see to ways to overcome this:
|
Yo, I'm from the future Here's what I did to make this work
Then deleted the libvips.so from the Kavita folder. Seems to work. This means, a proper pdfium binary could be included in the Kavita musl build now I think, to save us the trouble |
When running Kavita on Alpine Linux, PDF files can't be read, have a length of 0 and are without a cover.
To Reproduce
Steps to reproduce the behavior:
Error message
Error messages when a library with a PDF file is scanned (first warning) and Kavita tries to generate a cover (second warning)
Expected behavior
The PDF should be readable and have a cover
Screenshots
Looks like this in the web interface
The file can't be opened, with an error that Kavita can't read the archive
Desktop (please complete the following information):
Additional repositories were enabled to get all dependencies (pretty much copied from Ubuntu Dockerfile).
Here's the
/etc/apk/repositories
fileInstalling dependencies:
Additional context
I did try the method of removing
libvips.so.42
as noted in this issue hereThe
vips
package was installed to provide the library instead. No change.Alpine uses musl libc instead of glibc.
The CPU I use to run alpine supports sse4_2 (marked with stars)
OS Release output
The text was updated successfully, but these errors were encountered: