aboutsummaryrefslogtreecommitdiff
path: root/docker.nix
AgeCommit message (Collapse)Author
2022-01-04Add iana-etc for /etc/protocols to default packagesSandro
2022-01-01docker.nix: set correct permissions on /tmpWolfgang Thaller
2021-12-21Add cacert to /etc/ssl/certs in the docker imageRok Garbas
Fixes #5797
2021-12-16docker: fix image so that nix profile worksJohn Axel Eriksson
nix profile will otherwise throw this error: error: path '/nix/var/nix/profiles/default/manifest.nix' is not in the Nix store That's not entirely true since manifest.nix is within a directory in the nix store but nix profile seems to require the manifest.nix itself to be a store path.
2021-11-16Make docker.nix match Nixpkgs's idiomsJohn Ericson
1. `target` is the wrong name, that is just for compilers per out standard terminology. We just need to worry about "build" and "host". 2. We only need one `pkgs`. `pkgs.buildPackages` is how we get anything we need at build time. 3. `crossSystem` is the name of a nixpkgs parameter that is actually an attribute set, not a 2-part "cpu-os" string. 3. `pkgsCross` effectively evaluates Nixpkgs twice, which is inefficient. It is just there for people poking around the CLI / REPL (and I am skeptical even that is a good idea), and *not* what written code should use, especially code that is merely parametric in the package set it is given. 4. We don't need to memoize Nixpkgs here because we are only doing one pkg set at a time (no `genAttrs`) so it's better to just delete all this stuff. `flake.nix` instead would do something like that, with `genAttrs` (though without `pkgsCross`), if and when we have hydra jobs for cross builds.
2021-11-11docker.nix: Use 'with'Eelco Dolstra
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
2021-11-11Docker image with Nix insideRok Garbas