Prelude branch not building Elasticsearch #20
-
When building prelude branch of the conductor repo on Docker Desktop - it generates the following error:
The Elasticsearch logs produce the following:
The inspect panel produces the following:
This stops things immediately after the "Spinning up the Prelude Development Portal" message is triggered. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hey Corey, thanks for the detailed log, I was unable to reproduce the issue however it looks like Elasticsearch is running out of memory when trying to deploy, you can see this from the state objected in the ES log:
Two things I'd like you to try/confirm:
Adjust these in Docker Desktop settings under "Resources". If you already have these configured appropriately or are still having issues then try bumping up these values, I personally am running a cpu limit of
Let me know if this works! if not I'll ask some more questions to troubleshoot further. |
Beta Was this translation helpful? Give feedback.
Hey Corey, thanks for the detailed log, I was unable to reproduce the issue however it looks like Elasticsearch is running out of memory when trying to deploy, you can see this from the state objected in the ES log:
"OOMKilled": true, ..."ExitCode": 137,
where OOM is Out of Memory and 137 is saying docker does not have enough RAMTwo things I'd like you to try/confirm:
Adjust these in Docker Desktop settings under "Resources". If you already have these configured appropriately or are still having issues then try bumping up t…