-
Notifications
You must be signed in to change notification settings - Fork 18
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
Using Kotlin version of application in AWS Apprunner is failing with MultipartException #2
Comments
Thanks for reporting! Regarding the versions, the dash part that comes after the version number is the build number, that was introduced after creating the pipeline here: 2a81f75 Run #12 is the latest run , hence the latest version is: Before that, the images were being pushed manually (the A mistake from my part was not including metadata with the images about their respective commit hash. Regardless, both From the error message that i see, i could see that the root cause is You can manually that by calling the actuator health endpoints: $ curl localhost:8080/actuator/health
{"status":"UP","groups":["liveness","readiness"]} Let me know if that works so we can further narrow down the issue |
@duronxx for the fonts you may want to include the fonts used in the doucment manually in a seperate volume see this command: docker run \
--rm --name docx-to-pdf \
-p 8080:8080 \
-e "pool.size=1" \
-v ./fonts:/usr/share/fonts/custom \ <----------------------- Notice this volume
moalhaddar/docx-to-pdf:latest If the results above are from a the curl, you may want to save the output first to a pdf file curl --output file.pdf \
--location 'http://localhost:8080/pdf' \
--form 'document=@"/input.docx"' |
Im facing the same issue.
|
First of all, thank you for your work. You have provided a nice wrapper on libreoffice.
Here is the issue:
I deployed newest version (2.1.0-12 and 2.1.0-11) of docker image from https://hub.docker.com/r/moalhaddar/docx-to-pdf to AWS Apprunner and I received
I tried again with the same payload (same request, same image) locally and it was working fine.
My command (I tried with multiple files between 58kb and 4mb) :
I tried once again but with older version of your image (2.1.0) and this time it was working both locally and on AWS.
I have no idea what could cause this issue, but I see that both versions 2.1.0-12 and 2.1.0 are in Java.
Could you provide an information what are the commits between 2.1.0 and 2.1.0-11? I might find the issue and provide you a PR.
Best regards
The text was updated successfully, but these errors were encountered: