Kibana report generate using docker based configuration

Hi Team

We have Docker based multi-node ES cluster v7.17.4. Kibana also runs as a docker container.
When we try to generate a PDF report from Canvas, it shows following error:

Error: Max attempts (3) reached for job l7t1okam0006182da87b8f6b. Failed with: Error: Error spawning Chromium browser!

Detail log in Kibana console is as follows :

kibana | {"type":"log","@timestamp":"2022-09-08T12:55:39+00:00","tags":["info","plugins","reporting"],"pid":6,"message":"Scheduled PDF reporting task. Task ID: task:8a0eac90-2f75-11ed-b768-5120a0b2594a. Report ID: l7t1yoh9000653347bgcclsy"}
kibana | {"type":"response","@timestamp":"2022-09-08T12:55:39+00:00","tags":,"pid":6,"method":"post","statusCode":200,"req":{"url":"/api/reporting/generate/printablePdfV2","method":"post","headers":{"host":"localhost:5601","user-agent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0","accept":"/","accept-language":"en-US,en;q=0.5","accept-encoding":"gzip, deflate, br","referer":"http://localhost:5601/app/canvas","content-type":"application/json","kbn-version":"7.17.5","content-length":"319","origin":"http://localhost:5601","connection":"keep-alive","sec-fetch-dest":"empty","sec-fetch-mode":"cors","sec-fetch-site":"same-origin"},"remoteAddress":"172.19.0.1","userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0","referer":"http://localhost:5601/app/canvas"},"res":{"statusCode":200,"responseTime":268,"contentLength":756},"message":"POST /api/reporting/generate/printablePdfV2 200 268ms - 756.0B"}
kibana | {"type":"log","@timestamp":"2022-09-08T12:55:40+00:00","tags":["info","plugins","reporting","runTask","printablePdfV2","printable_pdf_v2","execute-job","l7t1yoh9000653347bgcclsy","browser-driver"],"pid":6,"message":"Creating browser page driver"}
kibana | {"type":"log","@timestamp":"2022-09-08T12:55:41+00:00","tags":["error","plugins","reporting","runTask","printablePdfV2","printable_pdf_v2","execute-job","l7t1yoh9000653347bgcclsy"],"pid":6,"message":"Error: Error spawning Chromium browser!\n at Observable._subscribe (/usr/share/kibana/x-pack/plugins/reporting/server/browsers/chromium/driver_factory/index.js:185:24)"}
kibana | {"type":"log","@timestamp":"2022-09-08T12:55:41+00:00","tags":["error","plugins","reporting","runTask"],"pid":6,"message":"Error: Error spawning Chromium browser!\n at Observable._subscribe (/usr/share/kibana/x-pack/plugins/reporting/server/browsers/chromium/driver_factory/index.js:185:24)"}
kibana | {"type":"log","@timestamp":"2022-09-08T12:55:41+00:00","tags":["info","plugins","reporting","runTask"],"pid":6,"message":"Rescheduling task:l7t1yoh9000653347bgcclsy to retry after error."}
kibana | {"type":"log","@timestamp":"2022-09-08T12:55:41+00:00","tags":["warning","environment"],"pid":6,"message":"Detected an unhandled Promise rejection: Error: Protocol error (Target.setDiscoverTargets): Target closed.\n at /usr/share/kibana/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:71:63\n at new Promise ()\n at Connection.send (/usr/share/kibana/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:70:16)\n at Function.create (/usr/share/kibana/node_modules/puppeteer/lib/cjs/puppeteer/common/Browser.js:118:26)\n at ChromeLauncher.launch (/usr/share/kibana/node_modules/puppeteer/lib/cjs/puppeteer/node/Launcher.js:109:56)\n at runMicrotasks ()\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at Observable._subscribe (/usr/share/kibana/x-pack/plugins/reporting/server/browsers/chromium/driver_factory/index.js:158:19)"}

On further debugging, we found that, this error does not come when Elasticsearch is setup without docker.
For docker based environment, it seems that the docker image of elasticsearch does not contain required libraries which are needed to generate report.

Can anyone please help on how we can use Kibana reporting functionality using docker based environment.

Appreciate any help on this.

Regards

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.