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.
You must log in or register to comment.
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.
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
deleted by creator
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?
It’s literally maintained by Fedora. Not sure why he claimed that.
Does it support the docker compose plugin / v2 API (the ‘docker compose’ plugin and not the old ‘docker-compose’ command)?
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?
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.because lennart poettering is an asshole.
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
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.
Most VMs only run containers, but I have supporting services on every host as well. Stuff like the mesh VPN, monitoring agent or firewall.
If I want a quick overview, a quicksystemctl statuswill tell me everything I need to know.What do you have set up for mesh VPN?
I use Yggdrasil now with a whitelist of public keys. Though I’m thinking about redoing my architecture in general to make key distribution easier, have more automated DNS entries and also use the tunnel for any node to node communication.
Before that I tried Tailscale with Headscale, but I didn’t want to have a single node responsible for the network and discovery.
That’s very interesting. Once you connect something to your mesh you can access the rest of the mesh by IP? What is the gateway in that case?
I have not seen quadlets before, that’s really neat.
Thanks!
Cool :)
Thanks for sharing!
You’re welcome, stay tuned for more posts about Quadlets.
