i am fiddling around with the new experimental PDF-Export Application. Problem is: Failure in Docker-Container, when exporting an PDF.
Docker Container is starting, automatically
Docker Container is not reused
Client-Side Export is working well
Failure Log of Container:
DevTools listening on ws://0.0.0.0:9222/devtools/browser/6d8f7c74-bf7c-4794-8645-7ed6dac19918 [0819/074613.837888:ERROR:gl_factory.cc(128)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none),(gl=egl-angle,angle=swiftshader)].
[0819/074613.842176:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization [0819/074613.856909:ERROR:gl_factory.cc(128)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none),(gl=egl-angle,angle=swiftshader)].
[0819/074613.866434:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization [0819/074613.877342:ERROR:gpu_init.cc(481)] Passthrough is not supported, GL is disabled, ANGLE is [0819/074613.932067:WARNING:dns_config_service_linux.cc(428)] Failed to read DnsConfig.
Is there any place where i can inject and try the Chromium Flag --no-gpu?
Thus, what you could do is configure the extension to not start the image automatically and instead start it manually (and reuse it probably). Then you should be able to use the --disable-gpu option from “How to use with WebGL” at https://hub.docker.com/r/zenika/alpine-chrome
Let us know if it works. It could be an improvement to add a configuration to pass additional “docker run” options.
Thx
PS: Would be interesting to understand why you get these errors on your system since disabling the gpu is probably not the best.
It would be very helpful to know exactly what we need to install to get PDF Export working.
A step by step description would be great.
The documentation is at least for me not obvious that you also need zenika/alpine-chrome:latest.
As described in my post, I also tried to install PDF inside Docker and failed, as before.
If the docker container runs on the same host as xwiki and xwiki is NOT itself in a container:
Install Docker
Add your tomcat-User (tomcat9?) to the docker group to allow starting and stopping a container
pull the image once (zenika/alpine-chrome:latest)
add the config from the extension page to xwiki.properties (as provided)
install the extension in the XWiki administration
Restart tomcat
If the docker container runs on the same host as xwiki and xwiki is itself in a container:
pull the image once (zenika/alpine-chrome:latest)
add the config from the extension page to xwiki.properties and
2.1 specify the host that the Chrome container can use to access XWiki. (IP or Name of the XWiki Container)
2.2 Set export.pdf.dockerNetwork=bridge to the network the xwiki-container is running in
install the extension
Restart the xwiki docker container
Does this help you?
(There is a third option where xwiki and headless-chrome docker container run on different machines. But for this please adapt the steps above and add ip addresses to the config )
We’re planning to remove that default Docker requirement in the future so that it works OOB without any configuration change, and explaining to Admin users how to set it up using docker if they need that.
That’s weird and should be reported since it would be a bug. Maybe you could try again? Could it be that you didn’t let it enough time to do the pull and stopped xwiki before it could finish?
Hello to you both,
I have tested both, with and without docker. One is installed on my Synology with docker and I test it like you described it @jwielsch. (everything internal Docker)
I test with changing xwiki.porperties or not and installing zenika/alpine-chrome:latest or not.
I get this error on Docker Versions:
