Alpine 3.19 have no package for libssl.so.1.1 causing the library to fail

[jotolo]

Description

Alpine 3.19 has removed the package for libssl.so.1.1. When trying to use this library within alpine 3.19 it fails due this issue.

Any idea or suggestion on how we could get it to work with Alpine 3.19?
I have tried installing libssl3 package but it didn't work. When using the gem it specifically request for libssl.so.1.1 library.

Any help would be very much appreciated. Thanks for creating this gem!

[Jonwheeler]

I am running into the same issue here. Were you able to find a resolution @jotolo?

[yuchylyak]

Same issue here when using ruby:3.2.2-alpine in Docker with wickedpdf.
On generating PDF it fails on:
`Error: PDF could not be generated!

web_1 | Command Error: pid 28 exit 127

web_1 | Error loading shared library libssl.so.1.1: No such file or directory (needed by /usr/local/bundle/bundler/gems/wkhtmltopdf-binary-edge-alpine-9ba05799c369/libexec/wkhtmltopdf-alpine-linux-amd64)

web_1 | Error loading shared library libcrypto.so.1.1: No such file or directory (needed by /usr/local/bundle/bundler/gems/wkhtmltopdf-binary-edge-alpine-9ba05799c369/libexec/wkhtmltopdf-alpine-linux-amd64)
`

[jotolo]

I am running into the same issue here. Were you able to find a resolution @jotolo?

@Jonwheeler I haven't been able to solve this issue. Sorry

[justpiyoosh]

I have tried this and it seems to be working for ruby:3.2.2-alpine

RUN echo "https://dl-cdn.alpinelinux.org/alpine/v3.15/main" >> /etc/apk/repositories && \
  apk add --no-cache \
  libssl1.1

[jotolo]

I've found a workaround to get the binary from the alpine version needed. You should stop using this gem or propose an update of the binaries with one of these solutions.

Getting the binary from Docker image

As suggested in the README file of this repository, you could run a command to extract the binary.
You just need to adjust the image name depending on the alpine version you are using.
You can see the list of tags available in https://hub.docker.com/r/surnet/alpine-wkhtmltopdf/tags

docker run --rm --entrypoint cat surnet/alpine-wkhtmltopdf:3.19.1-0.12.6-small /bin/wkhtmltopdf > ./wkhtmltopdf-alpine-linux-amd64

Getting the binary within Docker build

If you use Docker for your apps and need to have the binary into your docker image you can use a multi-stage build to copy the binary to your final image.

FROM surnet/alpine-wkhtmltopdf:3.20.2-0.12.6-small AS wkhtmltopdf

FROM ruby:3.3.4-alpine3.20

# Install wkhtmltopdf from previous stage
COPY --from=wkhtmltopdf /bin/wkhtmltopdf /usr/bin/wkhtmltopdf

[khalilgharbaoui]

Hi @jotolo first off thank you.

Indeed i added the instructions to the README with this situation in mind.

The suggestion you made to stop using this gem is unfortunately not an option for everyone. That is the main reason I made this gem, to just have a plug and play gem that takes care of the binaries.

You are more than welcome to contribute by opening a PR with the updated binaries in it, then we can rollout a new version of this gem and help everyone out that is already using it.

Thanks again.

[jotolo]

Hi @khalilgharbaoui,
I understand not everybody is able to jump right into one of these solutions.
I would like to help in this case. My only concern is regarding compatibility and releases.
I guess we will need to create releases for each one of the alpine releases? Is there any strategy on the versioning on this library we can use?
Maybe it is as simple as uploading the binary from alpine 3.20, the problem is I am not sure if it will work for previous versions too.
Any suggestion @khalilgharbaoui ?

[khalilgharbaoui]

Hi @khalilgharbaoui, I understand not everybody is able to jump right into one of these solutions. I would like to help in this case. My only concern is regarding compatibility and releases. I guess we will need to create releases for each one of the alpine releases? Is there any strategy on the versioning on this library we can use? Maybe it is as simple as uploading the binary from alpine 3.20, the problem is I am not sure if it will work for previous versions too. Any suggestion @khalilgharbaoui ?

Maybe we can keep the previous stuff as is, and find a way to distinguish between alpine os versions in our code and use that to load the new/right binary 🤔

@jotolo do you think this is a possible solution?

if that works or is even possible we could then simply bump the version and keep it backwards compatible.. at least for < 3.19 and > 3.20 maybe we can drop older ones later at some point, as more binaries means larger gem