10mo ago

Installing Jellyfin as a Podman Quadlet

ericthomas.ca

cross-posted from: https://lemmy.ca/post/30126699

I created this guide on how to install Jellyfin as a Podman Quadlet on your server. Enjoy.

Self Hosted - Self-hosting your services. @lemmy.ml

eric @lemmy.ca

10mo ago

Installing Jellyfin as a Podman Quadlet

ericthomas.ca /posts/jellyfin-quadlet/

Jellyfin: The Free Software Media System @lemmy.ml

eric @lemmy.ca

10mo ago

Installing Jellyfin as a Podman Quadlet

ericthomas.ca /posts/jellyfin-quadlet/

30 comments

Hey what is the advantage of quadlets over normal podman-compose?
- I've wondered myself and asked here https://lemmy.world/post/20435712 – got some very reasonable answers
- Podman compose is not maintained and should not be used.
  Qualets leverage systemd and a Kubernetes like system to create deployments that are much more dynamic. Basically you can manage your containers just like any other resource
  
  Who says that it is no longer maintained? https://github.com/containers/podman-compose Looks fine to me?
this guide, and the previous one, have a lot of weird superfluous steps. like, why use a command that includes nvim and then ask people to change it instead of just saying "edit the file"? why symlink systemd stuff to your own home directory?
the info is good, but having to separate the actually useful stuff from things that are specific to your config makes it less useful.
- I'm still learning how to write good posts. I'll this into consideration for the next one.
  
  your writing overall is good! it's just a matter of information priority.
  here's a tip, dunno how applicable it is but i use it when writing technical documentation:
  for each step, explain to yourself why you're doing it the way you are. if it turns out you caused the step to be needed, rather than it being required, you probably need to rethink, or at least add the explanation to the text.
I have not seen quadlets before, that's really neat.
- Thanks!
Why would someone want containers managed by systemd instead of just having them run like normal? What is the advantage?
Also if you use cockpit or some equivalent GUI to manage your containers, do you have to give it permission to control all systemd services?
- I've been managing my containers using the older mechanism (systemd-generate) since I started and it's great. You get the reliable service start of systemd and its management interface. Monitoring is consistent with all your other services and you have your logs in exactly one location.
  I really wouldn't want a separate interface or service manager just because I'm running containers.
  
  Do you run other things on your system other than containers? I have a VM that only runs containers so it really doesn't do anything else with systemd apart from the basics so I'm curious if there would be any advantage to me switching.
- Why would you not want containers managed by systemd?
  You get the benefits of containerisation and you don't have to learn the arcane syntax of some container engine or another.
  
  Dunno what's arcane about setting your network up once, crrate the compose (jn my case regular docker) and write sudo docker compose up -d.
  Literally using Linux in any way shape or form is more arcane than this.
  Just recently learning about NFS sharing. Sure, let's write the config in /etc/export and also edit the fstab config on the guest to auto-mount it. Don't forget the whole syntax ;)
  Not the mention the 100 different ways of setting up a static IP in each distro which differs slightly in any package/distro
  
  because lennart poettering is an asshole.
Cool :)
Thanks for sharing!
- You're welcome, stay tuned for more posts about Quadlets.

30 comments