-
-
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
Installation fails on macOS High Sierra 10.13.2 beta #1684
Comments
Yikes! I had tested this, but the users already existed. I will update my test tool to remove users ahead of time, and will look in to it. |
Ok, so you can get around this via: for i in `seq 1 8`; do
sudo /usr/sbin/sysadminctl interactive -addUser "nixbld$i" -fullName "Nix build user $i" -home /var/empty -UID "3000$i" -addUser "nixbld$i"
done but it'll ask for your password a bunch of times, unfortunately. I'm still looking in to a way to make this nicer for the user. |
|
i'm now happily using nix, so thanks for the workaround. for anyone else who might have stumbled upon this issue after copy-and-pasting an error message into google, please note that the shell script in the comment above has a small typo. the first line should be:
|
Fixed mine, thank you for the correction! I'm glad it worked :) |
It may be worth mentioning this issue at https://forums.developer.apple.com/community/beta/macos-1013-beta |
Same issue. High Sierra 10.13.2 Beta (17C60c). I concur with @orivej about it being worth mentioning the issue on the macOS beta forums, and specifically worth asking for whatever kind of help/wizardry/guidance that Apple's experts may have. |
The Nix manual documents the usage of |
Thanks! The sudo script did work for me. Could there be a way to at minimum to print a better/clearer error message if the build users aren't existing? For example, a pointer to the documentation for dscl, or a link to this github issue, or the script above? (E.g. anything that makes it clear that the Nix group knows about this, and is working on it, and has a workaround?) |
dscl seems to work ... for now ...! |
This
|
Just to note that the issue still exists, on non-beta High Sierra 10.13.2. And that after the work-around with creating nixbld users things seem fine. |
I'm seeing a side effect that the Nix users now show up on the login screen, and in the menu bar upper right fast user switcher. For comparison, other system-related usernames do not show up. What removes the Nix users from the login screen and/or fast user switcher? |
nix/scripts/install-darwin-multi-user.sh Line 470 in 1ca8e95
nix/scripts/install-darwin-multi-user.sh Line 501 in 1ca8e95
|
@orivej Thank you! If anyone else on this thread has a similar issue, here's what I did:
Then reboot, or at least log out and log back in. |
Does this mean we end up with a bunch of empty useless home directories under /Users? |
@copumpkin As far as I can tell yes. I'm a Nix novice. Can anyone expert here comment? [Edit: I was mistaken-- thanks @orivej -- the user entries are visible on my Mac by using the For whatever it's worth, as a novice user I personally prefer a simple setup as the default, such as the software creating one nix user, and also ideally naming the user "nix". This is because a simple setup tends to be faster and easier to start using successfully, and to document, and to troubleshoot if needed. (E.g. there would be only one broken user, and the creating script would not need a |
@copumpkin The |
Oh, interesting, thanks! |
It is an entry in the Directory Service.
…On Thu, Dec 14, 2017 at 5:22 PM Daniel Peebles ***@***.***> wrote:
Oh, interesting, thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1684 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAErrLtlTDwUsR2nvYcl1fIrf8aL6pnuks5tAZ-6gaJpZM4Qfrg->
.
|
I marked this as stale due to inactivity. → More info |
I marked this as stale due to inactivity. → More info |
This seems to be failing at a different point than #1582 .
The text was updated successfully, but these errors were encountered: