Kibana docker building from GitHub source


(Akash John) #1

Hi Team,

We are looking for building a Kibana docker image from GitHub. Version is a dependency for us because we are using ES 5.6.1.

Could you please let us know how can we build the image from source code provided?


(Thomas Neirynck) #2

Hi @john.akash,

would the official docker image work for you?


https://www.docker.elastic.co/


(Akash John) #3

@thomasneirynck, unfortunately no. We would like to make couple of changes to use from our end like,

  • Remove Dev Tools, Timelion, Management etc from Kibana
  • Add some custom icons
  • Make use of kibana without Xpack

That is why we are planning to make use of github code.

Could you please let us know how can we achieve this?


(kulkarni) #4

Hi @john.akash,
1) Removal of Dev tools - you can only enable or disable the Dev tools using console.enabled set to either True or False. https://www.elastic.co/guide/en/kibana/current/configuring-console.html

You can't disable Management/Timelion at the moment using the same trick, because it is not a separate plugin in Kibana.

  1. What do you mean by adding custom icons? Like Chnaging the Kibana logo for example? You can follow some discuss posts where they discuss the same:
    Replace the kibana logo?

  2. Kibana is built with X-Pack in the kibana -docker image. Until just the OSS image is made available on docker, you could probably do the following after x-pack installed:

RUN bin/kibana-plugin remove x-pack
and set XPACK_SECURITY_ENABLED, XPACK_GRAPH_ENABLED, XPACK_ML_ENABLED and XPACK_REPORTING_ENABLED tofalse.

There is always the OSS Kibana you could use too.

@thomasneirynck: you could throw more light on this as well.

Thanks
Rashmi


(Akash John) #5

Hi @rashmi,

Thanks for your quick response

You can't disable Management/Timelion at the moment using the same trick, because it is not a separate plugin in Kibana.

  • If we are doing the docker image building from GitHub code, is it possible to get this done?

What do you mean by adding custom icons? Like Chnaging the Kibana logo for example? You can follow some discuss posts where they discuss the same:.

  • Yes, that is what we are looking for and will try that method and get back to you.

Kibana is built with X-Pack in the kibana -docker image. Until just the OSS image is made available on docker, you could probably do the following after x-pack installed:

  • It got worked for me.

There is always the OSS Kibana you could use too.

  • We were able to see 6.1.1 OSS image, could you please share 5.6.1 OSS image link?

Apart from that could you please share us the steps to build docker image from GitHub code?


(Mark Walkom) #6

What you are asking is a completely custom Kibana build from source, removing some core components from Kibana that are not meant to be plug-and-play, and then all built into your own docker container.

That's not something we're comfy doing because it compromises too many things, so we can't help any further we're sorry to say.

If you'd like an OSS (ie no X-Pack) container of Kibana, then check out docker.elastic.co/kibana/kibana-oss:6.1.1, as mentioned here.


(Akash John) #7

Hi @warkolm,

Thanks for your quick response.

We are trying to grant Dashboard access only to the users, that is the reason why we are trying for customisation of Kibana.

Could you please let us know if we have an alternative for this use case, so that we can avoid this?

If I am going with "docker.elastic.co/kibana/kibana-oss:6.1.1", it seems to be not working with our ES version (5.6.0). The error which we are getting is

This version of Kibana requires Elasticsearch v6.1.1 on all nodes. I found the following incompatible nodes in your cluster: v5.6.0 @ 100.65.226.154:9200 (100.65.226.154), v5.6.0 @ 100.65.226.170:9200 (100.65.226.170), v5.6.0 @ 100.65.226.134:9200 (100.65.226.134), v5.6.0 @ 100.65.226.141:9200 (100.65.226.141), v5.6.0 @ 100.65.226.143:9200 (100.65.226.143), v5.6.0 @ 100.65.226.163:9200 (100.65.226.163)","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}

It would be great if you can share the docker image building steps as well from GitHub.


(Mark Walkom) #8

https://www.elastic.co/products/x-pack/security has all of that.

We didn't provide different containers for the 5.X releases sorry to say. But it should be easy to alter the container build file, instead of building from source.


(system) #9

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