It’s not the same. You then need to manage volumes separately from images, or if you’re mounting a host folder for the Jellyfin files then you have to manage those separately via the host.
Container images are supposed to be stateless. So then if you’re only banking up the volumes, then you need to somehow track which Jellyfin version it’s tied to, in case you run into any issues.
A VM is literally all of that but in a much more complete package.
i’d consider that all a good thing, but i can also see how it’s more work
they’re supposed to be stateless because it’s easier to manage, upgrade, etc… if you don’t want that, you can just use load/save/commit (or import/export: can’t remember off the top of my head which is which) and ignore volumes: it amounts to the same thing… there’s also buildpack rebase so you can swap out the base container and keep your top level changes for quick version upgrades that are super simple to roll back
It’s not the same. You then need to manage volumes separately from images, or if you’re mounting a host folder for the Jellyfin files then you have to manage those separately via the host.
Container images are supposed to be stateless. So then if you’re only banking up the volumes, then you need to somehow track which Jellyfin version it’s tied to, in case you run into any issues.
A VM is literally all of that but in a much more complete package.
i’d consider that all a good thing, but i can also see how it’s more work
they’re supposed to be stateless because it’s easier to manage, upgrade, etc… if you don’t want that, you can just use load/save/commit (or import/export: can’t remember off the top of my head which is which) and ignore volumes: it amounts to the same thing… there’s also buildpack rebase so you can swap out the base container and keep your top level changes for quick version upgrades that are super simple to roll back
I’ve never worked with buildpack, so that’s interesting