# Reporting Error in Kibana: Spawning Chromium Browser in Docker, Kibana 8 **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-reporting, docker\ **Created:** [March 24, 2022, 1:01pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574 "2022-03-24T13:01:40Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Kirubanandhan](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@Kirubanandhan](https://discuss.elastic.co/u/Kirubanandhan)\ **Post date:** [March 24, 2022, 1:01pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/1 "2022-03-24T13:01:40Z")
I am having issue in Report generation in Kibana v8. I am running in Docker. Getting like Chromium headless Browser error. After that i had ran Diagnostics. It shows the error that i need to disable sandbox. That also made. Still issue persists. ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/6/16dc6a5d12062bcf970138fc5599dd3d7d7bfc5e.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/9/6962fa0675411f2b4f0ee75737a3938e54710bc6.png) ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [March 24, 2022, 5:26pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/2 "2022-03-24T17:26:14Z")
@tsullivan @Marius_Dragomir do you know whats happening here? thanks, Bhavya ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [March 24, 2022, 7:02pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/3 "2022-03-24T19:02:12Z")
Hi, which Docker image are you using? Does the base image have all the dependencies needed for Chromium? See [Configure reporting in Kibana | Kibana Guide [8.11] | Elastic](https://www.elastic.co/guide/en/kibana/current/secure-reporting.html#install-reporting-packages) > It shows the error that i need to disable sandbox. That also made. You shouldn't have to touch this setting, but just to make sure, you entered `xpack.reporting.capture.browser.chromium.disableSandbox: true` in kibana.yml? ---
**Author:** ![Kirubanandhan](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@Kirubanandhan](https://discuss.elastic.co/u/Kirubanandhan)\ **Post date:** [March 25, 2022, 11:03am UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/4 "2022-03-25T11:03:09Z")
@tsullivan Please check the below. Below was my environment. Kindly help on it. > [@tsullivan](#): > > which Docker image are you using? Does the base image have all the dependencies needed for Chromium? [docker.elastic.co/kibana/kibana](http://docker.elastic.co/kibana/kibana) 8.0.0 > [@tsullivan](#): > > You shouldn't have to touch this setting, but just to make sure, you entered `xpack.reporting.capture.browser.chromium.disableSandbox: true` in kibana.yml? Below was my settings in kibana.yml server.name: kib01 server.port: 5601 server.host: "0.0.0.0" elasticsearch.hosts: ["[http://es01:9200](http://es01:9200)"] elasticsearch.username: "kibana\_system" elasticsearch.password: "**" #xpack.actions.enabled: true xpack.encryptedSavedObjects.encryptionKey: 3334b9d xpack.reporting.encryptionKey: 6c1a4d1ce**\* #xpack.security.encryptionKey: a40203059\*\*\* #xpack.actions.enabledActionTypes: ["\*"] xpack.reporting.kibanaServer.hostname: localhost xpack.reporting.kibanaServer.protocol: http xpack.reporting.capture.browser.chromium.disableSandbox: true xpack.reporting.kibanaServer.port: 5601 xpack.reporting.queue.timeout: 60000 ---
**Author:** ![TBragi](https://avatars.discourse-cdn.com/v4/letter/t/54ee81/32.png) [@TBragi](https://discuss.elastic.co/u/TBragi)\ **Post date:** [March 25, 2022, 1:20pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/5 "2022-03-25T13:20:20Z")
Ran into this issue when upgrading from 7.16.2 to 7.17.1 using the official docker image `image: docker.elastic.co/kibana/kibana:7.17.1`. It was fixed by adding to kibana.yml: ```auto xpack.reporting.capture.browser.chromium.disableSandbox: true ``` ---
**Author:** ![Kirubanandhan](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@Kirubanandhan](https://discuss.elastic.co/u/Kirubanandhan)\ **Post date:** [March 25, 2022, 1:26pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/6 "2022-03-25T13:26:16Z")
I have added this parameter even though still facing issue. ---
**Author:** ![TBragi](https://avatars.discourse-cdn.com/v4/letter/t/54ee81/32.png) [@TBragi](https://discuss.elastic.co/u/TBragi)\ **Post date:** [March 25, 2022, 1:31pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/7 "2022-03-25T13:31:18Z")
Strange ☹ .. A difference between my configuration and yours is I have not defined any of the following settings ```auto xpack.reporting.kibanaServer.hostname: xpack.reporting.kibanaServer.protocol: xpack.reporting.kibanaServer.port: ``` Could you try and disable those and see if it still happens? ---
**Author:** ![Kirubanandhan](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@Kirubanandhan](https://discuss.elastic.co/u/Kirubanandhan)\ **Post date:** [March 25, 2022, 2:02pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/8 "2022-03-25T14:02:01Z")
Yes i have tried earlier.. no success thats why added those also ---
**Author:** ![Kirubanandhan](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@Kirubanandhan](https://discuss.elastic.co/u/Kirubanandhan)\ **Post date:** [March 28, 2022, 10:13am UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/9 "2022-03-28T10:13:15Z")
@tsullivan any updates here. Need your inputs to fix this issue ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [March 31, 2022, 10:40pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/10 "2022-03-31T22:40:32Z")
How much RAM is available to the docker container? You'll want to start with 8 GB. Do you have a customized `config/node.options` file? If so can you provide the contents of it please? ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [March 31, 2022, 10:45pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/11 "2022-03-31T22:45:41Z")
> [@TBragi](#): > > Ran into this issue when upgrading from 7.16.2 to 7.17.1 using the official docker image `image: docker.elastic.co/kibana/kibana:7.17.1` . > > It was fixed by adding to kibana.yml: > > ```auto > xpack.reporting.capture.browser.chromium.disableSandbox: true > > ``` This seems strange. The Kibana reporting features should work without having to add any config properties. I filed an issue to investigate this: [[Reporting] Could not generate screenshot reports without manually disabling Chromium sandbox · Issue #129148 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/129148) ---
**Author:** ![Kirubanandhan](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@Kirubanandhan](https://discuss.elastic.co/u/Kirubanandhan)\ **Post date:** [April 1, 2022, 3:27pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/12 "2022-04-01T15:27:39Z")
```auto ## Node command line options ## See `node --help` and `node --v8-options` for available options ## Please note you should specify one option per line ## max size of old space in megabytes #--max-old-space-size=4096 ## do not terminate process on unhandled promise rejection --unhandled-rejections=warn ``` @tsullivan Kindly help on it. Do you really need 8GB of RAM?? ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [April 1, 2022, 7:10pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/13 "2022-04-01T19:10:40Z")
> [@Kirubanandhan](#): > > Do you really need 8GB of RAM?? It's not me 🙂 it's Chromium that needs it. When someone is on their laptop/desktop and using Kibana, they usually have 4-32GB. When they load a dashboard, it's done within an acceptable amount of time. If they try with a 1GB laptop, the browser wouldn't have enough resources to load Kibana or lanuch at all. The same principle is the case if you have a 1 GB server (I'm not saying you have 1GB - I don't know what you have). Chromium gets the "remainder" of memory not reserved by Kibana. In practice, it looks like Kibana rarely needs more than 1.5 GB of RAM. You can control the max memory that Kibana can reserve with the `--max-old-space-size=4096` line in `config/node.options` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 29, 2022, 7:11pm UTC](https://discuss.elastic.co/t/reporting-error-in-kibana-spawning-chromium-browser-in-docker-kibana-8/300574/14 "2022-04-29T19:11:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.