3 ms·
What does a container mean to you? On Nix there is no separation of file system or network across applications. The same installed libraries can be used by mul
by colordrops 4y ago
What does a container mean to you?
On Nix there is no separation of file system or network across applications. The same installed libraries can be used by multiple apps. Apps have access to the same system services and run together, e.g. with a single systemd. How can you call what Nix is doing "containers" ? There's virtually no overlap.
Zoom overtook the local freeway as the preferred mechanism for get to meetings at my company. I guess Zoom is a road by your logic.
- superkuh 4y agoOn Snaps there is no separation of network access. The same installed libraries can be used by multiple applications. Applications have access to the same system services and run together. How can you pretend Nix is different from a Snap container? There's virtually complete overlap. Or maybe you'll now say that Snaps are not containers because they do it in a Nix like way? By your logic a frontage road is not a road just because it's dedicated to a single commercial development and named differently. In my top level post which started this big thread I claimed that the purpose of containers (Nix, Snaps, Flatpack, Docker, AppImage, etc) is to solve the future shock problem and allow running of broken applications by controlling the libs available. I stick to that claim here.
- colordrops 4y agoI'm reading on snapcraft that most snap packages use "strict" confinement, which means that they "run in complete isolation, up to a minimal access level that’s deemed always safe. Consequently, strictly confined snaps can not access your files, network, processes or any other system resource without requesting specific access via an interface." Sounds like a container to me, and it's not how Nix does things.