Kibana exits due to changed password in config

[kennyparsons]

Problem description

I followed the initial setup instructions to change passwords for elastic and kibana_system (as well as all other default users). But before that, the command to just bring up elasticsearch didn't work:

docker-compose up elasticsearch -d
Creating network "docker-elk_elk" with driver "bridge"
ERROR: No such service: -d

So i pivoted and just did docker-compose up elasticsearch, which ran it in the foreground. No biggy. I ran the password commands in a separate window. I changed the passwords, edited the two config files mentioned, saved it, and moved on. So far so good.

Now i switch back to elasticsearch running in the foreground, kill it (ctrl-c), and then bring up the whole stack with docker-compose up -d.

I check the containers and kibana quits immediately. I checked the logs. The password generated started with an illegal character (*). So I put single quotes around it and it worked. Might be nice to have that defaulted to be in quotes, if passwords are randomly generated.

Extra information

The only remaining issue: docker-compose up elasticsearch -d didn't work. Any ideas why it does for you and not for me?

[antoineco]

You're right, that's entirely on me. The position of the flag needs to be swapped:

docker-elk/.github/workflows/ci.yml

Line 78 in 370ebbf

docker compose up -d elasticsearch

Regarding the quotes, it looks like you ran into a very unfortunate situation where the password started with either *, &, !, #, or any other "special" YAML character. I'll fix that too!

Thanks for reporting.