Unverified Commit fd80777b authored by Bongso, Suriyanto's avatar Bongso, Suriyanto Committed by GitHub

docs: Add Troubleshooting for Docker error 137 (#866)

ES crashed on the first call due to out of memory for ES query. Increasing Docker engine memory helps fix this issue.
parent 9bf21288
...@@ -76,3 +76,6 @@ Atlas would be ready once you'll have the following output in the docker output ...@@ -76,3 +76,6 @@ Atlas would be ready once you'll have the following output in the docker output
hard: 65535 hard: 65535
``` ```
Then check if all 5 Amundsen related containers are running with `docker ps`? Can you connect to the Neo4j UI at http://localhost:7474/browser/ and similarly the raw ES API at http://localhost:9200? Does Docker logs reveal any serious issues? Then check if all 5 Amundsen related containers are running with `docker ps`? Can you connect to the Neo4j UI at http://localhost:7474/browser/ and similarly the raw ES API at http://localhost:9200? Does Docker logs reveal any serious issues?
5. If ES container crashed with Docker error 137 on the first call from the website (http://localhost:5000/), this is because you are using the default Docker engine memory allocation of 2GB. The minimum needed for all the containers to run with the loaded sample data is 3GB. To do this go to your `Docker -> Preferences -> Resources -> Advanced` and increase the `Memory`, then restart the Docker engine.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment