this post was submitted on 25 Dec 2024
18 points (90.9% liked)

Jellyfin: The Free Software Media System

5895 readers
54 users here now

Current stable release: 10.10.5

Community Standards

Website

Forum

GitHub

Documentation

Feature Requests

Matrix (General Information & Help)

Matrix (Announcements)

Matrix (General Development)

Matrix (Off-Topic) - Come get to know the team and blow off steam!

Matrix Space - List of all the available rooms on Matrix.

Discord - Bridged to our Matrix rooms

founded 4 years ago
MODERATORS
18
Container vs service (self.jellyfin)
submitted 1 month ago* (last edited 4 weeks ago) by SailorsLife to c/[email protected]
 

The last post on the subject I could find was a year ago. So thought I would ask again. I have debian 12 up on miniPC and I have my NAS mounted. My intention is to use jellyfin and some of the arr* stuff. I know only a little about systemd (I just google what I need to know). I have some contianer knowledge, but mostly in k8s. And the docker parts aren't really my problem. But I have a vague understanding of docker. What are the latest pros and cons of containers vs service installation?

Edit: The opinions were unanimous. Containers it is.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 10 points 1 month ago* (last edited 1 month ago)

I am by no means an expert on this, but I find containerization/docker advantageous for two reasons:

  1. It's (relatively) easy to configure and spin up a container to try something out and/or put it into production. I prefer it with docker compose but you've got straight CLI options, GUI options like portainer, or OS deployments like yunohost or proxmox.

  2. The isolation and dependency management. Everything you need is in the container. No dependency conflicts with other things running on the system. And removing a container leaves the system nice and clean. Just prune your images and volumes and it's like it was never there.

Edit: grammar