-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
zsh: command not found: dotnet on Mac m1 #22910
Comments
Assuming you used the installer and it ran to completion, it will place the |
EDIT: I guess the answer is on the issue title. Mine's an intel mac and the installer seems to be working fine. |
cc @wli3 @dsplaisted since we're seeing multiple reports of this happening. |
@richlander @marcpopMSFT to route. Looks like an M1 Mac issue. |
Anyone have a work around? |
EDIT: ignore, see next comment. After installation the symlink is missing, which is likely due to SIP (System Integrity Protection).
It creates the file just fine, however terminal still can't see it. It looks like dotnet is installed correctly, but just can't be accessed... This is about as far as I have got. |
Nevermind, I had the path wrong:
The path has changed, so there's an /x64/ in there now. |
Getting many customer reports on this error: dotnet/core#6979 Could we please prioritize this? |
Hi folks, This issue should describe how the .NET SDK works on M1 machines and what we recommend: #22380 In general, you should only install the ARM64 versions of the SDK and not any of the x86 ones (uninstall them if you already did), and things will work a lot better. |
@dsplaisted This answer has been posted a few times, but it won't solve the entire issue. It seems as though the file path has changed, and so it's not getting linked correctly. The install paths for arm are missing /x64/ There are loads of helpful comments there, but could take a while for anyone to search through to find what works for them. Ideally the installer gets an update. |
This is not a valid solution to this issue. There are several frameworks that only support .net core 3.1 rather than the SDK which does not solve the issue of the command not working, thus microsoft should find a fix for this. |
For what it's worth, I only got this issue after upgrading to Monterey. It was fine on my M1 on Big Sur. Not sure what the upgrade did, but I verified the path had changed and created the symlink as above. |
Here is that issue again dotnet/core#7170 |
Lol this is seriously still a thing? |
With the version v6.0.102 the same error. I needed |
CC @richlander |
I use bash but still... I have a new m1 mac aka arm64 architecture
If you download both, you are going to have a nightmare of a time uninstalling correct versions and getting paths for dotnet correct, like I did. If you download So what did I do? 1.) I removed the 2.) then i download 3.) I installed rosetta via CLI which lets intel apps run on arm64 4.) Dotnet command still doesnt work cause arm64 chip is expecting a different path, so I use command from above 5.) I 6.) re-open terminal 7.) run |
Hi all, I've just encountered the
At this point I received the
Unfortunately I still received the error Like several commenters above, adding a symbolic link to Is this the "official" solution for now? I.e., is the symlink the only part of the installation that failed? (Happy to provide installation logs if they exist) |
Not official until they acknowledge the issue. |
I installed the ARM64 version and I have the same issue. |
MacOs 12.3.1, tried the above solutions but none seems to work |
cool |
|
brew install dotnet |
run this command and it will fix your issue |
This problem still exists, need to manually create a link after install |
The pathing problem is very difficult to solve because the there is no way to know where the installation happens without doing a lot of digging. IN: OUT: I need to find a way to install |
IN:
OUT:
I am not sure why Apple developed such a terrible chip in the M1. But, it is very difficult to navigate the terminal when the system denies the admin. Any advice would be appreciated. Thanks. |
I managed to install dotnet by using Homebrew:
|
chiming in here, Mac M1 as well and had this problem too. Symlink fix above worked for me. |
for Mac M1, you need to |
i using intel imac, my case erase all and reinstall dodtnet 6.0.x, refer it https://stackoverflow.com/questions/44089518/how-can-i-uninstall-dotnet-core-from-macos-sierra |
M1 Mac and the install location for dotnet is |
I am so stuck in this problem "dotnet not found" until I installed the .NET SDK Arm64 in this link |
M2 Pro and had the same issue for v7.0.203, this fixed the problem for me. Although v7 is in STS I am waiting for v8 to get out of preview. |
in Mac M1 you also need to create the bin folder in "/usr/local" if it does not exists sudo mkdir /usr/local/bin then you may run: sudo ln -s /usr/local/share/dotnet/x64/dotnet /usr/local/bin/ |
I had the same issue on Mac M1 as well and this command works for me Kudos to all the people sharing the solution above |
Had the same issue on MacBook Pro M1. Got dotnet bundled with Rider. Didn't have
You might need also to reload your profile to pick up changes. Also, be aware that on some systems these changes could be rewritten by other zsh shell-related configs. |
@GuySerg that worked for M2 as well. |
Thanks, worked for me with a M1 config, SDK 8 :
|
This is the perfect reply |
"sudo ln -s /usr/local/share/dotnet/dotnet /usr/local/bin " Enter this in terminal and then asks for password, then this issue gets solved . (My device is M1 Mac) |
I have macOS 12.0.1
When I open a project on visual studios, the message says that I need to install .net core 3.1. But when I download it, nothing changes and I still cannot run the the command dotnet
I would appreciate, if someone helped me
Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/install
Operating System: macos
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
The text was updated successfully, but these errors were encountered: