3 ms·
So this is mostly about Nix, but I've used (in production!) CoreOS, which implemented some of the same concepts. You couldn't just update anything easily. Well
by outworlder 7y ago
So this is mostly about Nix, but I've used (in production!) CoreOS, which implemented some of the same concepts.
You couldn't just update anything easily. Well, anything is possible, but CoreOS made it very hard to do it the wrong way, with the readonly system partitions.
But it made upgrades really easy. And you have a second, backup system partition to boot from, if the update messed up things.
We had to move back to a 'standard' Linux distribution and now all those old habits are creeping up. It takes a lot of discipline (and enforcement) to avoid the applications of 'fixes' which get eventually forgotten.
- yjftsjthsd-h 7y ago> We had to move back to a 'standard' Linux distribution and now all those old habits are creeping up That sounds very relevant: Why did you have to go back?
- ecnahc515 7y agoMost likely because Container Linux (previously CoreOS) is nearing end-of-life. Your options are to move to Fedora CoreOS or Flatcar Linux, so it's likely they decided to go with a more vanilla distro instead of migrating to one of the more similar options.
- yjftsjthsd-h 7y agoThat's actually a fairly encouraging failure mode, given that it means there's nothing inherently wrong with the approach, just that particular implementation.
- ghuntley 7y agoUpdates are easy. For an advanced example of overriding nixpkg and usage of pinning/override layers (ie some mandate or reason to run super old version of grpc) — https://github.com/digital-asset/daml/blob/master/nix/nixpkgs.nix#L10 https://github.com/digital-asset/daml/blob/master/nix/nixpkg...