Docker image bundles x-pack

[JorritSalverda]

Since moving the official docker image from docker hub to docker.elastic.co/kibana/kibana X-Pack is suddenly installed and enabled by default. I think most of the installations out there make use of the open source version which doesn't include X-Pack.

Of course it can be disabled by passing XPACK_MONITORING_ENABLED=false but then it starts with the following message:

Optimizing and caching bundles for graph, ml, kibana, stateSessionStorageRedirect, timelion, login, logout and status_page. This may take a few minutes

And once it's past this step Kibana doesn't work, it redirects me to /login?next=%2F and then chokes out with ERR_TOO_MANY_REDIRECTS in the Chrome browser. I started it with the following command:

docker run -d -p 5601:5601 -e "ELASTICSEARCH_URL=h***" -e "STATUS_ALLOW_ANONYMOUS=true" -e "XPACK_MONITORING_ENABLED=false" -e "ELASTICSEARCH_USERNAME=" -e "ELASTICSEARCH_PASSWORD=" -e "XPACK_MONITORING_UI_CONTAINER_ELASTICSEARCH_ENABLED=false" docker.elastic.co/kibana/kibana:5.5.0

Perhaps this is related to issue #8818?

Is it possible to create a separate docker container that doesn't have X-Pack installed? Tag 5.5.0-os or something alike?

[tylersmalley]

You also need to set the following:

XPACK_REPORTING_ENABLED=false
XPACK_SECURITY_ENABLED=false

[wvidana]

Seems odd not having a global disable xpack option but having to disable different settings all across the stack. In my case i thought that XPACK_SECURITY_ENABLED=false was enough, but i kept getting on the kibana logs a GET request to /api/reporting/jobs/list_completed_since?since.... Ended up disabling THREE different xpack options on kibana

xpack.security.enabled: false
xpack.reporting.enabled: false
xpack.monitoring.enabled: false

Not mentioning disabling the security option on ES and the monitoring option on Logstash. Really annoying https://www.elastic.co/guide/en/x-pack/current/xpack-settings.html

PS: @tylersmalley the reporting option was not enough for me on Kibana, I had to disable monitoring too.

[JorritSalverda]

Even when passing in those values using the following command:

docker run \
  -d \
  -p 5601:5601 \
  -e "ELASTICSEARCH_URL=https://***:443" \
  -e "STATUS_ALLOW_ANONYMOUS=true" \
  -e "XPACK_MONITORING_ENABLED=false" \
  -e "XPACK_REPORTING_ENABLED=false" \
  -e "XPACK_SECURITY_ENABLED=false" \
  -e "ELASTICSEARCH_USERNAME=" \
  -e "ELASTICSEARCH_PASSWORD=" \
  -e "XPACK_MONITORING_UI_CONTAINER_ELASTICSEARCH_ENABLED=false" \
  docker.elastic.co/kibana/kibana:5.5.0

Kibana doesn't start correctly. I get the following errors in the logs:

["status","plugin:elasticsearch@5.5.0","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2017-07-11T09:40:10Z","tags":["status","ui settings","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Elasticsearch plugin is yellow"}
{"type":"log","@timestamp":"2017-07-11T09:40:10Z","tags":["license","warning","xpack"],"pid":1,"message":"License information could not be obtained from Elasticsearch. [illegal_argument_exception] No endpoint or operation is available at [_xpack] :: {\"path\":\"/_xpack\",\"statusCode\":400,\"response\":\"{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"illegal_argument_exception\\\",\\\"reason\\\":\\\"No endpoint or operation is available at [_xpack]\\\"}],\\\"type\\\":\\\"illegal_argument_exception\\\",\\\"reason\\\":\\\"No endpoint or operation is available at [_xpack]\\\"},\\\"status\\\":400}\"}"}
{"type":"log","@timestamp":"2017-07-11T09:40:10Z","tags":["status","plugin:xpack_main@5.5.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - X-Pack plugin is not installed on Elasticsearch cluster","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2017-07-11T09:40:10Z","tags":["status","plugin:graph@5.5.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - X-Pack plugin is not installed on Elasticsearch cluster","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2017-07-11T09:40:10Z","tags":["status","plugin:searchprofiler@5.5.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - X-Pack plugin is not installed on Elasticsearch cluster","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2017-07-11T09:40:10Z","tags":["status","plugin:ml@5.5.0","error"],"pid":1,"state":"red","message":"Status changed from green to red - X-Pack plugin is not installed on Elasticsearch cluster","prevState":"green","prevMsg":"Ready"}
{"type":"log","@timestamp":"2017-07-11T09:40:10Z","tags":["status","plugin:tilemap@5.5.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - X-Pack plugin is not installed on Elasticsearch cluster","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2017-07-11T09:40:10Z","tags":["status","plugin:watcher@5.5.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - X-Pack plugin is not installed on Elasticsearch cluster","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2017-07-11T09:40:40Z","tags":["license","warning","xpack"],"pid":1,"message":"License information could not be obtained from Elasticsearch. [illegal_argument_exception] No endpoint or operation is available at [_xpack] :: {\"path\":\"/_xpack\",\"statusCode\":400,\"response\":\"{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"illegal_argument_exception\\\",\\\"reason\\\":\\\"No endpoint or operation is available at [_xpack]\\\"}],\\\"type\\\":\\\"illegal_argument_exception\\\",\\\"reason\\\":\\\"No endpoint or operation is available at [_xpack]\\\"},\\\"status\\\":400}\"}"}
Unhandled rejection [illegal_argument_exception] No endpoint or operation is available at [_xpack] :: {"path":"/_xpack","statusCode":400,"response":"{\"error\":{\"root_cause\":[{\"type\":\"illegal_argument_exception\",\"reason\":\"No endpoint or operation is available at [_xpack]\"}],\"type\":\"illegal_argument_exception\",\"reason\":\"No endpoint or operation is available at [_xpack]\"},\"status\":400}"}
    at respond (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:295:15)
    at checkRespForFailure (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:254:7)
    at HttpConnector.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:159:7)
    at IncomingMessage.bound (/usr/share/kibana/node_modules/elasticsearch/node_modules/lodash/dist/lodash.js:729:21)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

[wvidana]

@JorritSalverda I think your problem is that you don't have X-Pack installed on ES. Even if disabled i think it should be installed on ES so Kibana doesn't break. Really annoying, I know... (related elastic/kibana-docker#27)

Your original issue relates with elastic/kibana-docker#35

[jbudz]

I'm going to close this issue in favor of elastic/kibana-docker#27. I'm definitely +1 on making changes here, however we manage the docker image in that repo and I want to keep all the discussion in one place as much as possible.