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

Jellyfin: The Free Software Media System

5895 readers
36 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 3 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
[–] nottelling 3 points 1 month ago

The pro/con has more to do with how you want to run your system and manage changes.

Containerization is primarily about repeatability and declarative configuration management. If you want to repeat the same configuration with every deployment and/or upgrade, containers are the way to go.

If you want to tweak and manage the software the way you want it and aren't concerned with configuration drift, then install it as a service.