You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
to make the basic directory structure of Nix (part 1)
mkdir: /nix: Read-only file system
mkdir: /nix/var: Read-only file system
mkdir: /nix/var/log: Read-only file system
mkdir: /nix/var/log/nix: Read-only file system
mkdir: /nix/var/log/nix/drvs: Read-only file system
mkdir: /nix/var/nix: Read-only file system
mkdir: /nix/var/nix/db: Read-only file system
mkdir: /nix/var/nix/gcroots: Read-only file system
mkdir: /nix/var/nix/profiles: Read-only file system
mkdir: /nix/var/nix/temproots: Read-only file system
mkdir: /nix/var/nix/userpool: Read-only file system
mkdir: /nix/var/nix/gcroots/per-user: Read-only file system
mkdir: /nix/var/nix/profiles/per-user: Read-only file system
---- oh no! --------------------------------------------------------------------
Jeeze, something went wrong. If you can take all the output and open
an issue, we'd love to fix the problem so nobody else has this issue.`
I did try installing nix earlier using curl -L https://nixos.org/nix/install | sh
and I followed instructions online on how to delete it. Maybe that's the case. I missed something.
because it created a file in the ROOT directory that was read only.
The text was updated successfully, but these errors were encountered:
@FranciscoAndaur The underlying issue here is fixed in #4289 (but a new release hasn't been cut since it was merged), so I'll focus on trying to get you back on the road.
Did you have a Nix install before the initial attempt you mention? This sounds like what happens when you have a previous install that still has nix in /etc/synthetic.conf (or one that hasn't been rebooted since it was removed).
synthetic.conf causes macOS to create an empty read-only root folder which is intended to be used as a mount point for the Nix volume. There's a gap in the check used in the most-recent Nix release (2.3.10) that decides if you need a Nix volume before the install can continue.
If you find it there, I think you can proceed one of two ways:
remove the file if Nix is the only entry, or remove the line otherwise.
Check for nix in /etc/fstab. If you find it there, remove it via sudo vifs.
Check for an existing Nix volume (in the graphical Disk Utility, or with diskutil list). If so, destroy the data volume using the GUI or diskutil apfs deleteVolume <disk_identifier>.
Re-run whatever uninstall steps you used before.
Once you've got it cleaned up, reinstall with one of the below:
the official installer with the darwin volume creation flag: sh <(curl -L https://nixos.org/nix/install) --darwin-use-unencrypted-nix-store-volume --darwin
Installation failed
`---- sudo execution ------------------------------------------------------------
I am executing:
to make the basic directory structure of Nix (part 1)
mkdir: /nix: Read-only file system
mkdir: /nix/var: Read-only file system
mkdir: /nix/var/log: Read-only file system
mkdir: /nix/var/log/nix: Read-only file system
mkdir: /nix/var/log/nix/drvs: Read-only file system
mkdir: /nix/var/nix: Read-only file system
mkdir: /nix/var/nix/db: Read-only file system
mkdir: /nix/var/nix/gcroots: Read-only file system
mkdir: /nix/var/nix/profiles: Read-only file system
mkdir: /nix/var/nix/temproots: Read-only file system
mkdir: /nix/var/nix/userpool: Read-only file system
mkdir: /nix/var/nix/gcroots/per-user: Read-only file system
mkdir: /nix/var/nix/profiles/per-user: Read-only file system
---- oh no! --------------------------------------------------------------------
Jeeze, something went wrong. If you can take all the output and open
an issue, we'd love to fix the problem so nobody else has this issue.`
I'm using a MacbookPro from 2017
Steps To Reproduce
Expected behavior
nix installed properly.
nix-env --version
outputAdditional context
I did try installing nix earlier using
curl -L https://nixos.org/nix/install | sh
and I followed instructions online on how to delete it. Maybe that's the case. I missed something.
because it created a file in the ROOT directory that was read only.
The text was updated successfully, but these errors were encountered: