A practical question on OCI container layers versus Nix
are being compared through Nix, NixOS, containers, and bootc. Nix is valued because shared can be stored once in a cache and reused across several builds or user environments. The key question is whether work in a similar way across different images.
The important details are how shared layers are identified, how the system knows a layer is safe to reuse, whether those layers are cached, and where that cache lives. The practical concern is avoiding repeated copies of the same dependency when many are used on one machine.
Key points
- Nix is being discussed for its ability to reuse the same dependency across several builds.
- may also be shared across images, but the exact rules matter.
- Layer identity, s, and cache location are the main questions.
- Disk use becomes more important when one Mac mini runs many self-s.
- The comparison is useful, but it does not by itself decide which setup is better.