Hacker News new | ask | show | jobs
by RockRobotRock 980 days ago
Getting invidious to run was a gigantic pain for me. It definitely consumed all my RAM and crashed my system at least once.
4 comments
toastercat 980 days ago
It was definitely a pain in the ass before the official docker image. Have you tried that?
link
RockRobotRock 980 days ago
Thank you! I'll try the Docker image.
link
toastercat 979 days ago
No problem. And I meant to mention the Docker Compose config they have here [0]. This is what I use to self-host on my Raspberry Pi, and it works great. Just make sure to add a cron job that restarts the container every hour to get around the memory leak issue (my cron job is literally /bin/docker restart <container_name>)

[0] https://docs.invidious.io/installation/#docker

link
Karupan 980 days ago
As long as you aren’t hosting a public instance, the docker config in their docs should work fine. As for RAM consumption, I have set limits, so not sure if it’s actually happening.
link
unixfox 979 days ago
You mean when compiling? It's normal.

There are recommendations about the memory needed for compiling.

If you do not have enough RAM just use the docker image which is already precompiled.

link
turtlebits 980 days ago
Odd, I have the docker image running on a cheap 4gb VPS and it's been rock solid so far (set it up about a week ago).
link