Daiderd Jordan

The main reason for me is the fact that this still needs some manual work to build. I improved it with the last update but it's not using dockerTools yet.

I've not really used pullImage, but it's probably `nix-hash --flat --type sha256 `. Also note that the version images can change , you might want to use the date tags.

I assume having something like this higlight as python. ``` #!/usr/bin/env nix-shell #!nix-shell -i python3.6 -p "python36.withPackages (p: with p; [ pyyaml ])" import yaml print(42) ```

How? Unless I add a modeline it doesn't for me, standard shebang filetype detection only works for `#!/usr/bin/env foo` or `#!/bin/foo`.

This would require overlayfs otherwise this is possible with any image if nix installed on the docker host. I use the following alias with `DOCKER_HOST` pointing to my desktop. ```bash...

This is neat but I don't really want to add support for this unless the syntax is somewhat standardised by the community.

This is an issue with the setup not the container. It's trying to resolve nix-docker as a hostname so I'd look at /var/root/.ssh/configt first.

Does it have the correct permissions (600) and ownership?

Isn't that just a warning?

This seems a bit out of scope for this project, I made it as a bare minimum image to run nix-build in a completely isolated environment. If you also want...