Is the extra layer of indirection you don't like Docker or this nix -> Docker integration? Compared to just installing all your nix packages in one Docker laye

Is the extra layer of indirection you don't like Docker or this nix -> Docker integration? Compared to just installing all your nix packages in one Docker layer, this does introduce build complexity. But it's analogous to the complexity of a compiler for a static language... the thing that comes out is not more complex than what went in, so at least the complexity doesn't propagate. The images produced by this should be interchangeable with their single-layer counterparts; the caching will just be better when the code is rebuilt and re-distributed. If you're all-in on nix, does the container ecosystem even add value? The author of this software thought so, at least when he posted in 2018: "Tying in to the schedulers, orchestration, and monitoring is very valuable" Note, I have not used this; I'm just also frustrated by software development getting eaten by incidental complexity.