Post #1846770

@jonmsterling because at least within the Dockerfile I linked, nix will be seamlessly and automatically provisioned inside the container when building and running it. Dockerfiles aren't actually fully reproducible, while Nix is, so the idea is to avoid specifying project-level dependencies within the Dockerfile itself and leave that to nix. All the Dockerfile has is the system-level dependencies required for the nix package manager installation.