25 ms·
As a user, you don't really need to care about the number of containers since everything is managed by docker-compose or k8s (soon). The advantages of having mo
by zoriya 2y ago
As a user, you don't really need to care about the number of containers since everything is managed by docker-compose or k8s (soon).
The advantages of having more containers is that you can have specialized softwares. For example, the search system is based on meilisearch which makes it way better than what could have been done by just using postgres/sqlite.
It also makes distribution or replication built-in (for example, to have a transcoder on a remote computer), jellyfin/plex does not support this natively and users have written their own remote transcoder for that.
- freedomben 2y agoAre you planning to run these containers in the same Pod? And/or what is the deployable unit going to be?
- zoriya 2y agoNot sure yet, I'm a beginner at k8s and just started writing a helm chart on a branch/reading the documentation. I have devops friends to help me with my skill issues tho x)
- seabrookmx 2y agoOnly half kidding, but you've heard of processes right? :) Plex for example starts many transcoder instances within a single container for scalability. You don't _need_ to scale at the container level. There's pros and cons to each approach, but for the self-hosting crowd keeping the deployment simple may broaden your audience. A good example I have experience with is vaultwarden: people use it because it's a single container deployment as opposed to the complex and resource intensive setup bitwarden provides.