-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
writableStore=false still makes the host store writable in build-vm #63
Comments
I'm using linuxPackages_3_4 as kernelPackages, and I don't seem to have any 'aufs' module in the booted system. |
Only now I noticed that 'writableStore==false' was meant NOT to use aufs, but also to leave the store read-only. Well, in my case, it is not read-only. |
Stage 2 has this line at boot, related to some EC2 thing:
Maybe this is related? |
As a note, it shouldn't be a problem if the vm script weren't run by root. |
…ming Content address renaming
I marked this as stale due to inactivity. → More info |
I closed this issue due to inactivity. → More info |
I have a virtual machine, of nixos master, with writableStore=false.
I can't see any 'aufs' in "mount" listings, and it can write files to the host /nix/store.
I was just running "nix-channels --update" in the guest, and it complained unpacking the nixexprs.tar about some "utime: Operation not permitted". But the manifest got unpacked into the store, and that file is also in my host store, while "nix-store --check-validity" reports that it's not valid.
The text was updated successfully, but these errors were encountered: