Skip to content
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

Is this really using version 51 of weasyprint? #14

Closed
espechtcfe opened this issue Feb 17, 2021 · 1 comment · Fixed by #15
Closed

Is this really using version 51 of weasyprint? #14

espechtcfe opened this issue Feb 17, 2021 · 1 comment · Fixed by #15

Comments

@espechtcfe
Copy link

When I look in the requirements.txt file, I see that the weasyprint version is specified as version 51, which is what I hoped. However, when I start an interactive session using the following:
docker run -it -p 5001:5001 aquavitae/weasyprint /bin/bash

Then if I run the following command:
weasyprint --version
I get the following:
WeasyPrint version 0.31

Shouldn't I be seeing version 51 there?

@samjetski
Copy link

Hi @espechtcfe, unfortunately the version published on Docker Hub is quite a bit behind. #11 would fix this but could be a while off (depending on @aquavitae's availability?).

In the meantime, you can get the latest version by cloning this repository and building the image directly. This also gives you the opportunity to bump to a newer Weasyprint version if you wish.

sed -i 's/WeasyPrint==51/WeasyPrint==52.2/g' requirements.txt
docker build -t weasyprint:52.2 .
docker run --rm -it weasyprint:52.2 weasyprint --version

We made a few other changes and pushed it to a private container registry to make it easier to direct-run and deploy on our infrastructure. We're using Azure/ACR, but GitLab.com is a good free option if you need this, i.e. docker run registry.gitlab.com/youraccount/weasyprint:52.2.

aquavitae added a commit that referenced this issue Nov 2, 2022
chore: #14 update to weasyprint V56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants