elasticsearch create error about docker

[qmapDL]

setting data_dir permissions to 777 and running pelias as non root user seems to solve the issue

[missinglink]

Interesting.. the relevant error message here is Elasticsearch did not come up, check configuration.

I hope the step pelias elastic wait returned a non-zero status code.

@orangejulius, this user is running pelias commands as root using sudo, I vaguely recall that has caused issues in the past?

Can you please try running the command again as a non-root user.

You should not proceed with the other commands until the elastic wait command is successful.

[missinglink]

Can you please post a copy of your .env file and the elasticsearch section of your docker-compose.yml file?

[missinglink]

Two other things to try:

• Manually check that elasticsearch is running by opening localhost:9200 in your browser
• If it's failing for a configuration reason then you can check the logs, I put a section in the readme about that.

[missinglink]

I suspect the issue is to do with the file ownership permissions on your elasticsearch data directory not being writable by the user you're running the script as.

[missinglink]

I'm closing this issue as it resolved then reported issue.

We discussed today a solution to mitigate these permission errors in the future so hopefully it's no longer an issue for anyone after we land that PR (eta next week).

[orangejulius]

Hey @qmapDL,
The improvement in #55 should mean chmod 777 is no longer required. If you get a chance to test out that PR, let me know how it looks.

steps to test:

1. pelias elastic stop to kill the elasticsearch container
2. rm -rf $DATA_DIR/elasticsearch to clear out the old ES data dir and ensure a clean setup for testing
3. pelias elastic start. Elasticsearch should now come up, and $DATA_DIR/elasticsearch should have permissions that allow it to be read by UID 1000 (even if you ran the pelias helper script as root)