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

Jellyfin: The Free Software Media System

5885 readers
4 users here now

Current stable release: 10.10.3

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 2 weeks ago* (last edited 1 week 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] 4 points 2 weeks ago

Please use Dockge instead of Portainer.

Dockge makes it much easier to actually see what's happening in the deployment process and debug any issues, instead of presenting the error on a small popup that vanishes after 0.3 seconds, and it gives you much better feedback when you misconfigure something in your compose file. It also makes it much easier to interact with your setup from the command line once you feel comfortable doing that. And the builtin docker run to docker compose feature is really handy.

Newbies will find Dockge much friendlier, and experienced users will find that it respects their processes and gets out of the way when you want it out of the way.