No, you don’t. Containers are the endgame of a bunch of dumb people saying “I don’t like apt, so I’m going to make my own and it’ll be better in my own distro”, and now we have a hundred incompatible alternatives that are worse than apt, and no one knows how to deploy for all of them, so they give up and make a container.
Even if everyone agreed on Apt as the standard package format, wouldn’t you still need to create multiple packages for the various different versions of libraries each distro will still have depending on their release cycle? As far as I know, it can be done theoretically, but since libraries can often break ABI, it’s safer to bundle all dependencies, but then you’re not far off from an appimage in practice.
No, you don’t. Containers are the endgame of a bunch of dumb people saying “I don’t like apt, so I’m going to make my own and it’ll be better in my own distro”, and now we have a hundred incompatible alternatives that are worse than apt, and no one knows how to deploy for all of them, so they give up and make a container.
Even if everyone agreed on Apt as the standard package format, wouldn’t you still need to create multiple packages for the various different versions of libraries each distro will still have depending on their release cycle? As far as I know, it can be done theoretically, but since libraries can often break ABI, it’s safer to bundle all dependencies, but then you’re not far off from an appimage in practice.
Also, what are your thoughts on Richard Brown’s (of opensuse) talk on Flatpak, who was a prominent hater of containerized apps.