The declarative and idempotent container specification seems like a nice developer QOL improvement over docker but... > Containers built from Dockerfiles are d

The declarative and idempotent container specification seems like a nice developer QOL improvement over docker but... > Containers built from Dockerfiles are difficult to exactly reproduce This isn't true in my experience, at least for a level of exactness that could have an impact on the behavior of the software running in the container. I have been working with docker in various contexts for 5 years and have never experienced any issues related to reproducibility (which is pretty much the primary selling point of docker). To your point though, I can see how reproducibility issues could happen in theory, but since its not a problem in practice it doesn't make for a very compelling reason to try nix instead. Just to be clear, I'm not trying to disparage nix, it honestly sounds pretty interesting, especially as a way to automatically provision a local workstation (docker is not good at this), but I am still curious as to the practical tradeoffs in terms of nix vs docker as a tool for building containers.