4 ms·
I agree in principle, but it's worth pointing out that Snap is designed for end-user applications, so it's unlikely to be used on a server or in a Docker image
by adambyrtek 6y ago
I agree in principle, but it's worth pointing out that Snap is designed for end-user applications, so it's unlikely to be used on a server or in a Docker image built for deployment.
- fxtentacle 6y agoI agree in general, but my work involves website automaton, meaning the now empty chromium package. Plus I want my workstation to be as similar as possible to the deployment container to make debugging easier. So if I feel uncomfortable using Ubuntu 20 for my workstation, I should probably switch my deployment docker base image, too.
- adambyrtek 6y agoMakes sense, I personally don't mind snaps for proprietary applications (mostly Slack and Spotify) which are otherwise hard to discover and keep up to date on Linux, but I don't understand why Canonical would force this for Chromium which is already packaged and open source.
- simosx 6y agoHave a look at LXD. It creates system containers that are based on runtimes of most Linux distributions. You can stick to specific versions and are certain that those do not change.
- tomjupiter 6y agoIronically, LXD is a snap package in Ubuntu[0] [0] https://packages.ubuntu.com/focal/lxd https://packages.ubuntu.com/focal/lxd
- type0 6y ago> but it's worth pointing out that Snap is designed for end-user applications They started building it for IoT, whereas Flatpaks were designed for the desktop from beginning.