-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Nix 2.2 enabled sandboxing on Linux by default, breaking a bunch of installations by default #3000
Comments
Possibly related, installation under WSL 2 Ubuntu is also broken:
Disabling sandboxing seems to help:
With this workaround in place I was able to complete installation of Nix under WSL 2 simply by re-running the installation script. |
I marked this as stale due to inactivity. → More info |
This is still relevant mr bot, thank you |
Ubuntu 12.04, centos 6 an debian 8 are really old and I don't think we should spend time on them. debian9 and gentoo can probably be fixed by either installing rsync which should not be required on newer version IIRC. Edit: |
Ah, I had this problem yesterday on archlinux with very fresh updates, and I went to this issue from the archwiki where it was listed together with the workaound |
The workaround there tells to disable sandbox in nix config file, this is a important thing? Should that be disabled? |
@klarkc extremely, its akin to disabling sandboxing in docker, a malicious build script could read all your files send them off to a server and you'd never notice |
I marked this as stale due to inactivity. → More info |
bot begone |
I think it was the right idea to enable it by default, but probably having a way to detect its support first might be good.
The change broke installations for:
Grid comparison:
Open these up in to new tabs and swap between them to see the differences.
Full reports:
The text was updated successfully, but these errors were encountered: