-
Notifications
You must be signed in to change notification settings - Fork 347
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
support debian 12 bookworm (add new binaries) #162
Comments
@adamzapasnik please tell me how you solved this issue for now? What did you put in the Gemfile? |
@igorkasyanchuk I didn't modify a Gemfile. I updated docker images tags from: |
thanks for reply, trying what you suggested 👍 |
Bumping this. I also started getting this issue all of a sudden. I'm using
|
Same issue for us, fantastic blame pointing and solution suggesting from @igorkasyanchuk 🥳 we changed the base image from ruby-3.2.2 to ruby-3.2.2-bullseye |
Same issue for us,
we ugraded our server OS to debian 12 and started getting this same error, |
Just hit this trying an update to Bookworm. |
Fyi, it appears the binary has been build for bookworm, wkhtmltopdf/packaging#155 |
I DID IT! I was using I was able to install the correct
but then I got weird errors about glibc so I also switched to |
Sorry to poke this again, but will we see a new gem with the bookworm update? |
Works wonderfuly wonderfully for me. Thankx |
Please provide a new binary. I get the same error with the Docker image
|
Try |
@jalaj-hn, |
As I mentioned in #162 (comment) the binary for Bookworm exists, it's a matter of a PR here to include support for it. I see a few open PR's that add support for other distros/archs, so I am unsure if the project is active and would accept a PR. Given the state of https://github.com/wkhtmltopdf/packaging being archived, I do wonder how much longer can expect any of this to be supported. |
Well, originally there was really just a handful of "fat" binaries in this project, because that's what was distributed through official Then I'm not at all against adding support for more variants and versions, but something needs to be done to control how big this project gets, and I hesistate on accepting a binary without comparing it's checksum to an official release. I wouldn't want someone to get a poisoned binary from this project. |
@unixmonkey is "wkhtmltopdf/packaging" where the official releases live? If so then at least they have an official for Bookworm. I was also looking at #129 which is attempting to remove the bloat from all the binaries. Is that something worth doing considering the state of |
Debian 12 support (amd64/i386/arm64) is now in version |
some of ruby docker images were upgraded from debian bullseye to bookworm a few days ago. This error has started to occur since then:
gems/wkhtmltopdf-binary-0.12.6.5/bin/wkhtmltopdf_debian_10_amd64: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
Think we need new binaries for debian 12 something akin to #145
(My current workaround is to use bullseye images)
The text was updated successfully, but these errors were encountered: