I have a Nix package I'd like to bundle up into a docker container.
Specifically, I want to use Nix as a more expressive alternative to a Dockerfile to have faster (non-linear) image builds.
I've found documentation on dockerTools.buildImage but I'd like to have a minimal working example, and I'd also like to know what ends up being in the docker container.
The following example packages (using contents =) the pkgs.nginx nixpkgs package into a docker container:
docker load --input $(nix-build -E 'with import <nixpkgs> {}; pkgs.dockerTools.buildImage { name = "nix-htop"; contents = pkgs.htop; config = { Cmd = [ "/bin/htop" ]; }; }')
You can then run it with
docker run -it nix-htop
The contents of the container are pretty minimal, a single Docker layer:
docker save nix-htop | tar x --to-stdout --wildcards '*/layer.tar' | tar t --exclude="*/*/*/*"
./
./bin/
./bin/htop
./share/
./share/applications/
./share/man/
./share/pixmaps/
nix/
nix/store/
nix/store/gi5vvbjawzw1bakiksazbd50bvfmpmmc-ncurses-6.0/
nix/store/pa5nkrpd5hg5qp1dc4gmbd2vdhn1y3x2-htop-2.0.2/
nix/store/vn6fkjnfps37wa82ri4mwszwvnnan6sk-glibc-2.25/
Only htop and its dependencies (glibc, ncurses), 26 MB on my case.