-
-
Notifications
You must be signed in to change notification settings - Fork 15k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
warning: unknown setting 'extra-sandbox-paths' #102632
Comments
I think I find the issue Seems is related to nixFlakes entry in configuration.nix nix.package = pkgs.nixFlakes;
nix.extraOptions = ''
experimental-features = nix-command flakes
''; |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/warning-unknown-setting-extra-sandbox-paths/9836/2 |
This most likely is from https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/misc/nix-daemon.nix#L43 and caused by NixOS/nix@ff4dea6 |
If I use nix. package = pkgs.nixUnstable; I can't run even basic nix expressions
|
that would be |
Oh no! It seems like this breaks There is also a branch that tracks nixos-unstable with the fix cherry-picked called |
@kisik21 Do you mean a check for the Nix version? If so, the file in question already seems to have those in a few places. (here) Maybe something like this could work? (simplified) let
sandboxSetting = if versionAtLeast nixVersion "???" then
"sandbox-paths"
else
"extra-sandbox-paths";
in pkgs.writeFile "nix.conf" ''
...
${sandboxSetting} = ${toString cfg.sandboxPaths}
...
'' EDIT: It seems like having |
@leotaku great! ✨ when will it drip down to nixpkgs master and then nixos-unstable? |
@kisik21 From what I understand, the changes from Nix master trickle down into the Currently, a PR for upgrading |
{ pkgs, ... }: {
nix.sandboxPaths = ["/bin/sh=${pkgs.busybox-sandbox-shell}/bin/busybox"];
} This could help you if you use my fork branch and accidentally override your nix.conf's default sandbox path and break your system building process. |
I marked this as stale due to inactivity. → More info |
I hope we can close it as solved since multiple overlapping attempts (sometimes unsuccessful, like mine) to fix this issue happened and one of them got into the main branch. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Maintainer information:
The text was updated successfully, but these errors were encountered: