| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
The sandbox was (probably) enabled due to the .stack/shell.nix files: it made use of buildStackProject, which requires to run outside of the sandbox for some reason ( https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/haskell-modules/generic-stack-builder.nix#L25 ). Now that this file is not used anymore, we can reenable the sandbox.
It should help fix in particular this recent issue we’re facing in the CI: https://github.com/jfischoff/tmp-postgres/issues/251
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Mostly bugfixes inside nix itself ✨
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a partial revert of #7 where we added a copy of the initial
nix store to make sure it's not lost when we use a volume for the /nix
mounting point in the container.
However this was an unecessary duplication.
The initial nix store is already present in the docker image and can be
retrieved by using a “named” volume with `-v nix-store:/nix`, docker
will copy the /nix path of the image inside a volume called
`nix-store` on the host machine for us we don't need to it manually.
Of course if mounting an empty directory from the host machine (with
`-v /tmp/nix-store:/nix`) then the image won't boot (because docker
will NOT copy the content of the /nix path inside the image into the
/tmp/nix-store path of the host machine).
This change drastically reduces the image size (basically /2 as we
were duplicating the biggest source of disk space…)
```
REPOSITORY TAG IMAGE ID CREATED SIZE
docker-nix 2.3.4-vol f74209e25515 About a minute ago 1.58GB
docker-nix 2.3.4 61880484ceb1 12 minutes ago 835MB
```
Let's be 🍃 instead of ⛰️
|
| |
|
|
|
|
| |
These changes will allow the nix store to be mounted as a volume and
still be able to launch a bash console with the correct nix
environment.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
