Hannah (always eepy) :blobcat_sleep: on Nostr: nprofile1q…qrcc0 Technically NixOS could be described as a *non-containerized* ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqdhnn6acp8d933rcmkrw8vceqfhyfr26jw4a9katmwqhqelwkc50swqrcc0 (nprofile…rcc0) Technically NixOS could be described as a *non-containerized* dockerfile. A very complicated dockerfile (That would undersell it and is wildly simplifying things overall, but let's roll with that for a second).
"Packages" (or derivatives) are not containerized. They are read-only though and declare their dependencies inside themselves (the package.nix file I think? I am not that deep into the ecosystem.... yet).
The point of NixOS is reproducibility (mostly, there is also immutability and rollback functionality). The same directives in a .nix file should yield the same output.
So if I write into my config the following:
services.sshd.enable = true;and give the config to someone else and they build it on their computer, the output should be the same (in this case: A system that has a sshd server running).
"Packages" (or derivatives) are not containerized. They are read-only though and declare their dependencies inside themselves (the package.nix file I think? I am not that deep into the ecosystem.... yet).
The point of NixOS is reproducibility (mostly, there is also immutability and rollback functionality). The same directives in a .nix file should yield the same output.
So if I write into my config the following:
services.sshd.enable = true;and give the config to someone else and they build it on their computer, the output should be the same (in this case: A system that has a sshd server running).