Here is a decent example of a docker image being created from nixPkgs https://github.com/input-output-hk/plutus#how-to-run-a-local-plutus-playground-in-a-docker

Here is a decent example of a docker image being created from nixPkgs https://github.com/input-output-hk/plutus#how-to-run-a-local-plutus-playground-in-a-docker-container https://github.com/input-output-hk/plutus#how-to-run-a-local... Another advantage is a unified development environment as I can run the server in the container or directly on host machine in an isolated nix-shell. Yet another advantage, is unlike the layer of a docker container, isolated dependencies are isolated and linked so packages link together based on a hash-address/path of a dependency in the nix store so there is no need to worry about order of steps but rather what depends on what making the cache misses in a nix-store vs a docker layer more efficient. For example if the first step in a Dockerfile needs to be changed all proceeding steps need to be rebuilt where as if a dependency in a nix file say paython-2 to python-3, every package that depends on python just get re-linked and only those packages need to be updated and you already have python-3 used in a nix-shell or in another container odds are it's already cached and ready to go!