.NET Runtime Not Found While Running Dotnet Global Tools

[phadkesharan]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When attempting to run a .NET global tool, the application fails to locate the .NET runtime, even though the runtime and tools location have been added to the PATH variable. This issue persists despite following the recommended environment variable settings.

error message while running dotnet-ef

You must install .NET to run this application.

App: /home/phadkesharan/.dotnet/tools/dotnetsay
Architecture: x64
App host version: 8.0.5
.NET location: Not found

Learn more:
https://aka.ms/dotnet/app-launch-failed

Download the .NET runtime:

Expected Behavior

The global tool should execute without errors, locating the .NET runtime as specified in the environment variables.

Steps To Reproduce

Environment
Operating System: [Specify your OS and version, e.g., Ubuntu 22.04]
.NET SDK Version: [Specify the .NET SDK version installed, e.g., 8.0.5]
Architecture: x64

Steps to Reproduce

1. Install .NET SDK and runtime following the official installation instructions.
2. Add the following lines to the ~/.bashrc file:

   # Dotnet Core
   export DOTNET_ROOT=$HOME/.dotnet
   export PATH=$PATH:$DOTNET_ROOT:$DOTNET_ROOT/tools

3. Source the ~/.bashrc file:

   source ~/.bashrc

4. Install a global tool, for example:

   dotnet tool install --global dotnet-ef

5. Attempt to run the global tool:

   dotnet-ef

Exceptions (if any)

No response

.NET Version

8.0.105

Anything else?

No response

[martincostello]

dotnet/aspnetcore#55894 (comment)

[amcasey]

#55894 (comment)

Seems like dotnet/sdk based on related issues.

[Forgind]

Wow, didn't expect a seg fault:

root@WIN-7LIIBK7D2V8:~# dotnet tool install --global dotnet-ef

Welcome to .NET 8.0!
---------------------
SDK Version: 8.0.300

Telemetry
---------
The .NET tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.

Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry

----------------
Installed an ASP.NET Core HTTPS development certificate.
To trust the certificate, view the instructions: https://aka.ms/dotnet-https-linux

----------------
Write your first app: https://aka.ms/dotnet-hello-world
Find out what's new: https://aka.ms/dotnet-whats-new
Explore documentation: https://aka.ms/dotnet-docs
Report issues and find source on GitHub: https://github.com/dotnet/core
Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli
--------------------------------------------------------------------------------------
An issue was encountered verifying workloads. For more information, run "dotnet workload update".
You can invoke the tool using the following command: dotnet-ef
Tool 'dotnet-ef' (version '8.0.6') was successfully installed.
root@WIN-7LIIBK7D2V8:~# dotnet-ef
Segmentation fault

No idea where that's from, but I don't think it's the SDK...

[marcpopMSFT]

Triage: I think Forgind's report is different than the originally issue. @phadkesharan any chance you can collect a host trace from your original repro? https://github.com/dotnet/runtime/blob/main/docs/design/features/host-tracing.md

[phadkesharan]

Triage: I think Forgind's report is different than the originally issue. @phadkesharan any chance you can collect a host trace from your original repro? https://github.com/dotnet/runtime/blob/main/docs/design/features/host-tracing.md

I was able to solve the issue by doing a reinstalling. I think the issue arose when installing dotnet sdk and runtime with apt package in ubuntu. Installing them via the installation script solved the issue completely

https://learn.microsoft.com/en-us/dotnet/core/install/linux-scripted-manual#scripted-install

[marcpopMSFT]

Triage: Since you got this resolved and it seems related to how you installed, we're going to close for now. Feel free to ping if there's more for us to investigate.

[mayvazyan]

I experienced the same issue when it was installed via snap. Reinstalling it via script worked for me as well.