Selfhosted

Use docker, once you're comfortable with it then switch to Podman. Podman has a few more complications, so it's easier to get the base thing running using the most common tool, and work from there.

I'm a pretty Podman novice guy too but I'm running quadlets since it automatically creates and runs these containers just like the other services would be with systemd. In terms of networking I can usually access to my container via publishing a port and using the PC's IP where the container is running, and this is the default network that Podman uses initially.

I have a Jellyfin quadlet config, that may help you. I've had numerous sufferings to make a working one, but here you go (These 3 files are in ~/.config/containers/systemd/jellyfin):

Description=Jellyfin Media Server
After=network.target

[Container]
Image=lscr.io/linuxserver/jellyfin:latest
PublishPort=8096:8096
Volume=jellyfin-config.volume:/config:Z
Volume=jellyfin-cache:/cache:Z
Volume=/home/USERNAME/media/storage1/Filmek:/data/Filmek:Z,U
Volume=/home/USERNAME/media/storage1/Sorozatok:/data/Sorozatok:Z,U

[Service]
Restart=on-failure

[Install]
WantedBy=default.target

[Unit]
Description=Jellyfin Cache Volume

[Volume]

[Unit]
Description=Jellyfin Config Volume

[Volume]

Please do ask questions if you have any. ^^

Podman is quickly becoming shit as Red Hat continues to remove features and recommend you use Kubernetes. I ended up removing it from my servers and switching to Debian from Fedora because I don’t like Red Hat mucking about with our open source community software.

I still run Docker.

For me the value of podman is how easily it works without root. Just install and run, no need for sudo or adding myself to docker group.

I use it for testing and dev work, not for running any services.

I use podman at work, mostly just a Docker replacement. My biggest problem with it is typing "pdoman" in commands by mistake.

I use podman mainly because it's very easy to manage using systemd services. Unfortunately, the command for generating these service files, podman-generate, is deprecated and won't receive new features.

Auto updating is done just using a simple tag and enabling a systemd timer to do it regularly for you.

It's easiest to start with the rootful mode, you won't have additional settings to set and no issues with permissions, UIDs and networking.

For networking, I always create a network per service I want to run. For example Nextcloud and its database would go in one network and you'd only forward the port for the webinterface for outside access.

In addition to networks I also use pods, this basically groups the containers together to start/stop them as one. If you use this, you have to set your port forwarding here.

The pi 3B+ is not powerful enough for all that. I would get a used minipc as even a old one will run circles around the old Broadcom CPU.

Podman is similar to docker except for the fact that it is daemonless and rootless by default. To expose things on lower ports you will need to battle permissions. Also podman has pods like kubernetes.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

3 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.

[Thread #908 for this sub, first seen 6th Aug 2024, 12:35] [FAQ] [Full list] [Contact] [Source code]

Not related to containers but I've had quite a lot of success using NixOS as the host OS. Setting up services like jellyfin is as simple as adding services.jellyfin.enable = true; to the config file.

I switched from Docker to Podman, because Podman is more secure (if rootless) but it was just hard to autostart containars. You have to start one by one because they don't have a central service like docker. And watchtower and nextcloud AIO don't work on Podman. So I switched back to docker.

My humble POV it's to stick with whatever do the work.