3 ms·
Getting invidious to run was a gigantic pain for me. It definitely consumed all my RAM and crashed my system at least once.
by RockRobotRock 3y ago
Getting invidious to run was a gigantic pain for me. It definitely consumed all my RAM and crashed my system at least once.
- turtlebits 3y agoOdd, 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).
- toastercat 3y agoIt was definitely a pain in the ass before the official docker image. Have you tried that?
- RockRobotRock 3y agoThank you! I'll try the Docker image.
- toastercat 3y agoNo 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 https://docs.invidious.io/installation/#docker
- Karupan 3y agoAs 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.
- unixfox 3y agoYou 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.