Closed Getslow6 closed 1 month ago
I think error Command failed with exit code 137
indicates docker ran out of memory. You'll either need to allocate more memory, add swap or stop some other addons to free up memory.
I'm also running into this. My server has around 3.5 GB of free memory. Starting Ghostfolio is fine, but as soon as I open the webinterface of Ghostfolio, RAM usage explodes into an OOM error, crashing multiple services on the host.
This is a hard no for me, even though I would've really liked to use Ghostfolio.
I think
error Command failed with exit code 137
indicates docker ran out of memory. You'll either need to allocate more memory, add swap or stop some other addons to free up memory.
I think you're right. I think we can close this, as this does not have to do with your addon but with Ghostfolio itself? Still strange that a web application like this requires so much RAM.
I have to pull back my report, it seems the issue is Alexa Media player
, which is eating up alll the RAM in version 2024.10 of HA.
In my case, this might be the underlying issue,not Ghostfolio.
Hi!
First of all; thank you for making this docker image into a Home Assistant addon.
I've tried installing the addon and followed the following steps:
Then I get the following logging (logging is of a second run, the first run applied some database migration scripts):
Do you know what might go wrong here? Thanks in advance!
System information: Core: 2024.9.1 Supervisor: 2024.09.1 Operating System: 13.1 Frontend: 20240906.0 Hardware: Intel NUC