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.

6 points
*

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?

permalink
report
reply
4 points

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.

permalink
report
parent
reply
-1 points

because lennart poettering is an asshole.

permalink
report
parent
reply
1 point

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

permalink
report
parent
reply
16 points

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.

permalink
report
parent
reply
1 point

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.

permalink
report
parent
reply
3 points

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 quick systemctl status will tell me everything I need to know.

permalink
report
parent
reply
1 point

Cool :)

Thanks for sharing!

permalink
report
reply
5 points

You’re welcome, stay tuned for more posts about Quadlets.

permalink
report
parent
reply
8 points

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.

permalink
report
reply
4 points

I’m still learning how to write good posts. I’ll this into consideration for the next one.

permalink
report
parent
reply
4 points

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.

permalink
report
parent
reply
3 points

That’s a good tip. Thanks. I think I might tweak the existing posts for readability.

permalink
report
parent
reply
1 point

I rewrote my original quadlet article, can you have a look and let me know what you think? https://ericthomas.ca/posts/setting-up-podman-quadlets/

permalink
report
parent
reply
7 points

I have not seen quadlets before, that’s really neat.

permalink
report
reply
3 points

Thanks!

permalink
report
parent
reply
16 points

Hey what is the advantage of quadlets over normal podman-compose?

permalink
report
reply
-10 points

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

permalink
report
parent
reply
21 points

Who says that it is no longer maintained? https://github.com/containers/podman-compose Looks fine to me?

permalink
report
parent
reply
14 points

It’s literally maintained by Fedora. Not sure why he claimed that.

permalink
report
parent
reply
3 points

Does it support the docker compose plugin / v2 API (the ‘docker compose’ plugin and not the old ‘docker-compose’ command)?

permalink
report
parent
reply
2 points

I’ve wondered myself and asked here https://lemmy.world/post/20435712 – got some very reasonable answers

permalink
report
parent
reply
1 point
Deleted by creator
permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 3.7K

    Monthly active users

  • 3.7K

    Posts

  • 79K

    Comments