-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Building from sources ERR005 #538
Comments
The updated error message shows that HTMLDOC is unable to connect to the server:
As I am unfamiliar with Alpine Linux, does it provide any firewall or kernel security features (SELinux, AppArmor, etc.)? Are there messages getting logged to any of the system logs about HTMLDOC? |
yes, there are firewall for AlpineLinux but none of them comes enabled by default and I am not enabling it either.
no as far as I can tell. Is there a way to add more verbose debugging so we can check what is going on here? |
The "host is down" message ( |
Ok, turns out that I was wrongly connecting to the wrong Docker container, PHP-FPM does not run any web server, I have Apache running in a different container. Pointing the URL to the Apache container makes that error go away. This is working as expected. Closing this |
Coming from #537 I am trying to get htmldoc build from sources using Docker containers and this is what my
Dockerfile
looks like:After build the htmldoc in a stage I am using the binary in another image as follow:
running
htmldoc --version
inside that image returns1.9.21
which means the binary gets build and is copied over to the destination image, generate a PDF is "working" but I cannot get image served through http/https to be part of the generated PDF. This is how the HTML looks like:This is an example HTML that is not working for me at the moment:
None of the above links work and I end up with the following "error" in the docker logs:
This is the command I am using to generate the PDF from the command line:
is there any way to debug this to check if a library is missing or what is the root cause?
The text was updated successfully, but these errors were encountered: