Closed MartinJohns closed 2 years ago
@jom @MartinJohns that is indeed a new restriction in v8.0.0. Thanks for the tip regarding the service account.
The instructions from the Initial setup
section of the README also allow you to run Kibana using the kibana_system
built-in user. We recommend all users to follow these steps the first time they set up their stack. Now this has suddenly become even more relevant so we should emphasize that these steps MUST be followed.
In kibana/config/kibana.yml change user to kibana_system, then docker-compose build; docker-compose up -d then change password for kibana_system:
curl -u elastic -XPUT 'http://myhost:9200/_security/user/kibana_system/_password' -H 'Content-Type: application/json' -d '{ "password" : "changeme" }'
The documentation was updated to better emphasize the need to initialize and use the kibana_system
user instead of the elastic
user in Kibana.
One alternative to this manual setup would be to create a setup
service inside the Compose file, as demonstrated in the Elastic documentation at Start the Elastic Stack with Docker Compose, but this approach feels a bit "hacky" to me. For example, it will break as soon as the user updates the bootstrap password of the elastic
user.
Problem description
The Kibana container fails to start due to the pre-configured user "elastic"
Extra information
Git Commit: 33a96e571a816b3417542496de16bbb2dfeb5afe
This is most likely due to the recent update to 8.0.
Stack configuration
No changes. Just clone, build and start.
Docker setup
Container logs