-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
macOS Catalina install fails on insufficient permissions to create volume #5198
Comments
I know you requested a full log @abathur but there really isn't much to report since it fails pretty early on. The only message out of the ordinary is the one shown above. |
Most-interested in the log to see how it's invoked; can just edit that in and omit the rest, I guess. |
To clarify a little (mostly for later travellers), this issue is almost certainly narrower than this. A fair number of people have confirmed the installer to be working on ~normal Mac hardware with ~normal nonvirtualized macOS installs, but we've also had a slow trickle of hard-to-debug issues with virtualized/cloud/CI setups. (partial backstory in #4779 and #3156)
My initial guess (because of the In a small set of Google search results drilling down on this I see a number of VMWare Fusion users turning up. I'm curious if you're just seeing a slightly different part of this elephant than others have reported. What does |
so the provisioning script is open here: You'll see here I am using the stable installer, that's because these machines are live and in production so I never committed the failed attempt to upgrade. Just imagine calling numtide/nix-unstable-installer on this line instead The output of your command is: if I read those two linked issues correctly it's different |
True is what we're hoping for, at least. I have a few ideas, but I'll be happy if we can sudo our way through it. I pushed a test commit to my fork that adds sudo back to the addVolume invocation; you should be able to adapt FWIW, this change cuts a corner for testing; if this works it'll still take a little more brainpower to make a full fix. |
Thanks for the script, but the curl command above just returns: {"error":"No such file install"} |
Sorry, it's been a few months; grabbed the wrong URL out of the test. I've updated it above (and linked to where the installer URL shows up in the test output). |
so it looks like we are back to the hash mismatch like the other scripts you sent me:
|
It shouldn't be hitting releases.nixos.org if you're specifying the |
this is how it was invoked:
|
It looks like the outer installer only handles |
okay that finally worked. I still saw the errors about |
These make me a little squeamish, but perhaps they're just noise. Will your next-step be to put these installs through the paces? If so, I'm interested in hearing how that goes. I'll also try to find a little time to try this out on a spare macbook. |
Yes well I can say that this "noise" never occurred with the stable install script, so it might be something, but so far none of our CI pipelines seem to mind the update on the one machine I'm testing this on atm. |
As reported in NixOS#5198, volume creation can fail with a permission error for some macOS users (probably secondary user accounts?) Sudo appears to be sufficient to avoid this. While I'm here, I also updated the sudo invocation added in 079bde2 to use the _sudo explanation wrapper.
I used a spare macbook running an 11.4 BigSur beta for a fairly basic test of the same installer you tried and didn't have any trouble. I've opened #5202 with a more-realistic swing at this and tested it on my spare macbook, if you can give it a try as well. The installer url is https://abathur-nix-install-tests.cachix.org/serve/ns7vmm072i37y0zf1nwkvz9v4qzklrga/install this time. |
As reported in NixOS#5198, volume creation can fail with a permission error for some macOS users (probably secondary user accounts?) Sudo appears to be sufficient to avoid this. While I'm here, I also updated the sudo invocation added in 079bde2 to use the _sudo explanation wrapper.
As reported in NixOS#5198, volume creation can fail with a permission error for some macOS users (probably secondary user accounts?) Sudo appears to be sufficient to avoid this. While I'm here, I also updated the sudo invocation added in 079bde2 to use the _sudo explanation wrapper.
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/what-is-the-recommended-installer-to-use-macos/15138/1 |
Describe the bug
Originally reported: nix-community/nix-unstable-installer#13
and: #4994 (comment)
@abathur requested I start a new issue since it is not exactly like #4994
Essentially an install fails on Mac OSX Catalina with the following error:
Steps To Reproduce
Expected behavior
Install should work as it did before #4289
Additional context
We use a pristine image of Mac OSX running as a zfs volume, which is then provisioned with a script which install Nix and some other required stuff (like secrets). I can trivially destroy and reprovision this image as needed for testing.
The text was updated successfully, but these errors were encountered: