dotnet command not found: 1.0.1 install on clean macOS Sierra

[leecow]

On macOS Sierra, (fresh install) the latest installer didn't set the correct path - dotnet in terminal returned command not found

OS version
macOS Sierra
Repro steps
Fresh install of macOS without prior dotnet core
Repro code (if you can share it / is relevant)
Error messages
command not found
Whether this worked before
Method of installing .NET Core
package installer

Ran

ln -s /usr/local/share/dotnet/dotnet /usr/local/bin

and started working

/cc @h3smith @blackdwarf

[blackdwarf]

@leecow can you check if you have dotnet in /etc/paths.d/ location?

[leecow]

@blackdwarf I haven't seen this repro. @richlander can you have a look at the machine where this was repro'd?

[the-darkvoid]

Can confirm this issue on a fresh macOS Sierra installation on a MacBook Pro.
Running .NET Core installer does not make the dotnet command available in the terminal.

@blackdwarf,
Path /etc/paths.d does not exist at all.
/etc/paths exists as a file containing:

• /usr/local/bin
• /usr/bin
• /bin
• /usr/sbin
• /sbin

[KiltedViking]

F.Y.I.: I had the same problem on one of my three Macs. The difference between failing Mac (2011) and others, should it help:

• I'm on the beta program track, i.e. just got latest beta for macOS 10.12.1.
• I don't have XCode installed - only command line tool (for Homebrew, etc.).

They are all running Sierra and the other computers are a Mac Mini (2012; never reinstalled "clean") and a Macbook Pro (less than 1 year old). I installed .NET Core last year, i.e. "DNVM", on all of them.

I added link and I could run the command dotnet.

[blackdwarf]

@the-darkvoid thanks for that info. Can you try the following please and let me know if it fixes it:

mkdir -p /etc/paths.d
echo /usr/local/share/dotnet > /etc/paths.d/dotnet

You may need to sudo both of the commands. This mimics the behavior of our postinstall step in the CLI installer. After these commands are done, open up a new terminal window and see if the command is on the $PATH now. (Of course, if you already symlinked it, please remove the symlink.)

Thanks much for your help!

[the-darkvoid]

@blackdwarf,

Creating the paths.d entry manually as suggested makes the dotnet command work.
Question remains is why the installer was unable to create these paths.d entries automatically.

Let me know if I need to dump some logs from the installer process.

[blackdwarf]

@the-darkvoid because the installer assumes that the /etc/paths.d exists. It did, I believe, on El Capitan. That means that we have an issue for the post-install step.

Any logs you can provide would be good. I guess this needs to go into the "known issues" document for Sierra.

[richjoslin]

The "sudo mkdir" works for me, but then the "sudo echo" line gives me this for some reason (tried with and without sudo):
-bash: /etc/paths.d/dotnet: Permission denied

update 1: (did chmod to 0777 and that let me do it - I'll take it, for now)

update 2: dotnet command still not found after that, here's my echo $PATH:
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

[blackdwarf]

@richjoslin what is in the /etc/paths.d/dotnet file?