Skip to content

Packaging comparison

lwbt edited this page Nov 19, 2024 · 4 revisions

Packaging comparison

⚠️
This is a draft.
ℹ️
AppImage also exists, but is out of scope for this comparison since such a package does not exist yet.
Native packaging (.deb) Flatpak Docker Kubernetes

Availability

Limited, not available on immutable systems

Most common Linux Distributions

n/a, requires Docker/Podman

n/a, required Kubernetes

Package Configuration

CLI

GUI (Flatseal), CLI

Mostly CLI

Mostly CLI

User and Permissions

Runs as jellyfin user, configured during installation

Runs as the same user who installs the Flatpak

Components and Dependencies

some older components and dependencies, dependent on Debian stable

newer components and dependencies, dependent on free desktop runtimes

Depends on the images used

Depends on the images used

Uninstallation

integrated into apt system, not all packages might be removed during uninstall

independent and easy to remove, just uninstall

Automatic Updates

configure unattended upgrades

Gnome-Software, Systemd Timer, see here

integrate something like watchtower? which is not recommended?

write an operator in go an package your application for every aspect of the app lifecycle (sounds like the totally right thing to do, but how many end users will arrive at this level of mastery?)

Setting up HTTPS

Many, options, available

Tailscale can be integrated easily, others eventually too

Refer to Docker Compose solutions in the official documentation

Easy peasy when you figured out the everything that came before

While it might be easier to install and run, it is not intended to be just a beginner friendly toy you want to move off after a few months. However, I have not heard of large scale, large user base, fault tolerant Flatpak deployments. For simple home usage it should be sufficient.