Docker kibana plugin installation with external dependencies error


I try to install our plugin with external dependencies( using Kibana docker image. I tried 7.3.0 and 7.3.1
On local machine I could install the plugin by coping it builded code to the plugins folder and running kibana with
bin/kibana -plugin-path='home_dir/plugins/my_plugin'

This approach doesn't work with docker.

Here is the error I've got:

 kibana_1         | {"type":"log","@timestamp":"2019-09-20T14:59:08Z","tags":["info","optimize"],"pid":1,"message":"Optimizing and caching bundles for graph, monitoring, space_selector, login, overwritten_session, logout, logged_out, ml, dashboardViewer, apm, code, maps, canvas, infra, siem, uptime, biei_73, kibana, stateSessionStorageRedirect, status_page and timelion. This may take a few minutes"}
kibana_1         | events.js:174
kibana_1         |       throw er; // Unhandled 'error' event
kibana_1         |       ^
kibana_1         | 
kibana_1         | Error: write EPIPE
kibana_1         |     at WriteWrap.afterWrite (net.js:782:14)
kibana_1         | Emitted 'error' event at:
kibana_1         |     at onwriteError (_stream_writable.js:431:12)
kibana_1         |     at onwrite (_stream_writable.js:456:5)
kibana_1         |     at _destroy (internal/streams/destroy.js:40:7)
kibana_1         |     at Socket._destroy (net.js:607:3)
kibana_1         |     at Socket.destroy (internal/streams/destroy.js:32:8)
kibana_1         |     at WriteWrap.afterWrite (net.js:784:10)
biei_73_kibana_1 exited with code 1

I built kibana with plugin image

FROM kibana:7.3.0
ENV PATH /usr/share/kibana/bin:$PATH
COPY --chown=kibana build/my_plugin /usr/share/kibana/plugins/my_plugin

My compose file:

version: '3'

      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
      - discovery.type=single-node
        soft: -1
        hard: -1
      - "9200:9200"
    image: kibana_browser:0.2.0
      - "5601:5601"
    command: /usr/share/kibana/bin/kibana --plugin-path=/usr/share/kibana/plugins/my_plugin

I'm not sure what that error means. Can you try adding the --verbose option to your command? Maybe you can get more details.

Here is the output with verbose added:

The verbose logs did not help much. I wonder if you can increase the available memory in your container? Someone had a similar error and said increasing the memory resolved it.

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