-
Notifications
You must be signed in to change notification settings - Fork 108
Unable to start Kibana 5.3.0 without X-Pack #27
Comments
Indeed. That's ugly, sorry. Even with all X-Pack components disabled: services:
kibana:
image: docker.elastic.co/kibana/kibana:${ELASTIC_VERSION}
environment:
- XPACK_GRAPH_ENABLED=false
- XPACK_MONITORING_ENABLED=false
- XPACK_REPORTING_ENABLED=false
- XPACK_SECURITY_ENABLED=false ...the exeception is still thrown:
For now, I would create a custom image with: FROM docker.elastic.co/kibana/kibana:5.3.1
RUN bin/kibana-plugin remove x-pack && \
kibana 2>&1 | grep -m 1 "Optimization of .* complete" # [1] Would it be worth have a single flag to truly disable all X-Pack functionality? @ycombinator? [1] See elastic/kibana#6057 for the optimization trick. |
That particular exception is being thrown because there is apparently no x-pack installed on the Elasticsearch side. I can see the value in having a single flag to disable all of X-Pack but it seems to me the issue here might be that the kibana docker image is doing too much? Maybe there should be a base kibana docker image that is only OSS kibana, and another one that layers on the x-pack plugin via |
@ycombinator @jarpy any update on this? we try to build our own custom images which does the |
We will likely release an OSS-only image soon. What's going wrong with your custom image? |
Have you used this env setting as well? |
the workaround we found was to still use the image form docker hub which doesn't have xpack installed and works great (unless the 5.1.2 does) |
I am just running kibana container like this:
|
|
you could just use the old docker hub image: https://hub.docker.com/_/kibana/ which doesn't have xpack at all it supports up to 5.6.0...hopefully they will have this fixed before that version |
With version 5.6.0 out where can we find the OSS version that doesn't depend on x-pack? Since the Kibana image on Docker Hub is no longer updated I guess half the world is waiting in suspense for it to arrive :) |
Yeah, this is pretty frustrating - I'm trying to update to Kibana 5.6 to resolve some gauge rendering issues (amongst other things) and it's not available on Docker hub, but the version on the Elastic Docker hub doesn't appear to be fit-for-purpose if you're not running X-Pack. Do we have an ETA for the OSS package, and is there a workaround in the meantime? |
Until we get a fix I just built my own image FROM docker.elastic.co/kibana/kibana:5.6.0
RUN bin/kibana-plugin remove x-pack and set |
@blacksails any chance you could publish your image or share your dockerfile? |
@fsosa well my comment contains everything in my dockerfile ;) |
What was motivations to not build automaticly oss flavor ? It would be really appreciated if Elastic registry could host oss docker image. I've tried Regards, |
bump would love to see the OSS images published standalone, to avoid people going down the road of their own forks as it seems others already are. |
Ouch! :) Sorry for the slow process here. We'll be shipping pre-packaged, OSS-only images as an option with the next 6.0 release candidate. We're also working with Docker Inc. to continue support for the existing 5.x series OSS images on Docker Hub. |
interesting option, thx. |
This seem quite active https://hub.docker.com/r/blacktop/kibana/ |
Hey, I've notice that it's effectively ready to pull image from -oss flavor for versions 6.x.x (ie: docker pull docker.elastic.co/kibana/kibana-oss:6.1.1). Thank you very much about that! |
You are welcome! Thanks for reminding me that we can close this issue. |
Hello, I tried @blacksails solution to uninstall xpack in kibana Dockerfile but the initialization is still quite slow.
Here is my config : Dockerfile
config/kibana.yml
docker-compose.yml
Am I missing something ? |
@yogeek Have you considered running the -oss image flavor instead? The |
@dliappis Sorry I have forgotten to precise that I have to use the 5.6.5 version and oss flavours are not yet available |
@yogeek Sorry I missed that you used <6.0.0 So you need to trigger a bundle reoptimization (which Kibana doesn't do after remove, but does after install) as shown in the example: #27 (comment) . There is a kibana issue in elastic/kibana#6057, it's not related to Docker. So change your Dockerfile
I was successful running docker-compose.yml and Dockerfile uninstalling kibana
|
Explicitly running |
@dliappis Great it works ! |
It would be nice if the oss variants were at https://www.docker.elastic.co/# (which is linked to from https://www.elastic.co/guide/en/kibana/current/docker.html). Can I file an Issue? |
@melissachang you can click the arrow next to the version for all variants. |
Ah thanks, I totally missed that. |
Our ElasticSearch 5.3.0 cluster does not have X-Pack installed, and I have no plans to install it.
However, when running Kibana 5.3.0 Docker image, it consistently switches to Red status due to the cluster not supporting X-Pack. How do you disable it completely?
I am running Kibana locally as below...
docker run -e ELASTICSEARCH_URL=http://10.2.8.243:9200 -e KIBANA_INDEX=.kibana -e XPACK_SECURITY_ENABLED=false -e XPACK_MONITORING_ENABLED=false -e SERVER_NAME:localhost -p 5601:5601 docker.elastic.co/kibana/kibana:5.3.0
The text was updated successfully, but these errors were encountered: