Skip to content

Correct Snap alias and symlink commands for .NET 10 SDK on Ubuntu 24.04.3 #54806

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.

Sign up for GitHub

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

Merged
adegeo merged 11 commits into from
Jul 16, 2026
Merged

Correct Snap alias and symlink commands for .NET 10 SDK on Ubuntu 24.04.3 #54806

Changes from all commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
c20bd23
Initial plan
Copilot Jul 15, 2026
e61e548
Fix Snap alias and symlink commands for .NET 10 SDK docs
Copilot Jul 15, 2026
208f8b0
Revise Snap SDK doc for versioned packages and command mapping
Copilot Jul 15, 2026
7d8439b
docs: remove misleading snap runtime targeting statement
Copilot Jul 15, 2026
e442ecf
docs: remove --classic from snap SDK install command
Copilot Jul 15, 2026
7f36b6b
Revise installation instructions for .NET SDK on Linux
adegeo Jul 15, 2026
5ac3ff5
Remove linux-release-wait include from SDK install
adegeo Jul 15, 2026
484ab90
Potential fix for pull request finding
adegeo Jul 15, 2026
82d0f9c
Add symbolic link instructions for dotnet command
adegeo Jul 15, 2026
4b6512e
Add mixed-install warning to intro and symlink scope note in section 2
Copilot Jul 15, 2026
38e12b6
Fix gerund phrase in section 2 symlink scope note
Copilot Jul 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
108 changes: 33 additions & 75 deletions docs/core/install/linux-snap-sdk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: Install .NET SDK on Linux with Snap
description: Learn about how to install the .NET SDK snap package. Canonical maintains and supports .NET-related snap packages.
author: adegeo
ms.author: adegeo
ms.date: 04/23/2026
ms.date: 07/15/2026
ms.topic: install-set-up-deploy
ms.custom: linux-related-content, updateeachrelease
ai-usage: ai-assisted
Expand All @@ -16,6 +16,9 @@ This article describes how to install the .NET SDK snap package. .NET SDK snap p

A snap is a bundle of an app and its dependencies that works across many different Linux distributions. Snaps are discoverable and installable from the Snap Store. For more information about Snap, see [Get started](https://snapcraft.io/docs/tutorials/get-started/#tutorials-get-started).

> [!IMPORTANT]
> If you install .NET with Snap, use Snap to manage all your .NET installations. Avoid mixing Snap with other installation methods, such as a package manager or the scripted install, because mixing methods can cause conflicts.

> [!CAUTION]
> Snap installations of .NET may have problems running [.NET tools](../tools/global-tools.md). If you wish to use .NET tools, we recommend that you install .NET using the [`dotnet-install` script](linux-scripted-manual.md#scripted-install) or the package manager for the particular Linux distribution.
>
Expand All @@ -36,60 +39,48 @@ Your Linux distribution might already include snap. Try running `snap` from a te

## 1. Install the SDK

[!INCLUDE [linux-release-wait](includes/linux-release-wait.md)]

Starting with .NET 9, snap packages for the .NET SDK are published under version-specific identifiers (for example, `dotnet-sdk-90` for .NET 9 and `dotnet-sdk-100` for .NET 10). Prior to .NET 9, all SDK versions were published under the same identifier `dotnet-sdk`, and you specified the version through a channel. Additionally, .NET 9 and later snap packages support both x64 and Arm64 architectures, while earlier versions only support x64. The SDK includes both the ASP.NET Core and .NET runtime, versioned to the SDK.
To install the .NET SDK, use version-specific snap package identifiers because this approach lets you install and manage multiple SDK versions side by side. For example, use `dotnet-sdk-80` for .NET 8 and `dotnet-sdk-100` for .NET 10. The SDK includes both the ASP.NET Core and .NET runtime, versioned to the SDK. This article uses the .NET 10 SDK snap package; if you're using a different package, substitute it.

> [!TIP]
> The [Snapcraft .NET SDK package page](https://snapcraft.io/dotnet-sdk) ([.NET 9](https://snapcraft.io/dotnet-sdk-90), [.NET 10](https://snapcraft.io/dotnet-sdk-100)) includes distribution-specific instructions on how to install Snapcraft and .NET.
> The Snapcraft .NET SDK package page ([.NET 8](https://snapcraft.io/dotnet-sdk-80), [.NET 9](https://snapcraft.io/dotnet-sdk-90), [.NET 10](https://snapcraft.io/dotnet-sdk-100)) includes distribution-specific instructions on how to install Snapcraft and .NET.

01. Open a terminal.
01. Use `snap install` to install the .NET SDK snap package.

The `--classic` parameter is required.

- **For .NET 9 and later**

Install the version-specific package. For example, the following command installs .NET SDK 10:

```bash
sudo snap install dotnet-sdk-100 --classic
```
The following command installs .NET SDK 10:

- **For .NET 8 and earlier**

Install from the `dotnet-sdk` package and specify a channel. If this parameter is omitted, `latest/stable` is used. For example, the following command installs .NET SDK 8:

```bash
sudo snap install dotnet-sdk --classic --channel 8.0/stable
```

The `dotnet` snap alias is automatically created and mapped to the snap package's `dotnet` command.
```bash
sudo snap install dotnet-sdk-100
```
Comment thread
adegeo marked this conversation as resolved.

The following table lists the snap packages and channels you can install:
The following table lists the .NET SDK snap packages you can install:

| .NET version | Snap package or channel |
|--------------|----------------------------------------|
| 10 (LTS) | `dotnet-sdk-100` (preview) |
| 9 (STS) | `dotnet-sdk-90` |
| 8 (LTS) | `dotnet-sdk --channel 8.0/stable` |
| .NET version | Snap package |
|--------------|------------------|
| 10 (LTS) | `dotnet-sdk-100` |
| 9 (STS) | `dotnet-sdk-90` |
| 8 (LTS) | `dotnet-sdk-80` |

## 2. Export the install location
## 2. Map the dotnet command

The `DOTNET_ROOT` environment variable is often used by tools to determine where .NET is installed. When .NET is installed through Snap, this environment variable isn't configured. You should configure the *DOTNET_ROOT* environment variable in your profile. The path to the snap uses the following format: `/snap/{package}/current`.
Because Snap doesn't create an unversioned `dotnet` command, create a symbolic link to make `dotnet` available system-wide. Create this link only if you want to map the `dotnet` command to this specific Snap installation. If you already have .NET installed through another method and you create this link, it overwrites that mapping.

For .NET 9 and later, use the version-specific package name:
If `/usr/local/bin/dotnet` already exists, remove it before you create the link.

```bash
export DOTNET_ROOT=/snap/dotnet-sdk-100/current
sudo ln -s /snap/dotnet-sdk-100/current/usr/bin/dotnet /usr/local/bin/dotnet
Comment thread
adegeo marked this conversation as resolved.
```

For .NET 8 and earlier, use the shared package name:
## 3. Export the install location

Configure the `DOTNET_ROOT` environment variable in your shell profile because tools use it to determine where .NET is installed. Snap installations don't set this variable automatically. The path uses the following format: `/snap/{package}/current/usr/lib/dotnet`.

```bash
export DOTNET_ROOT=/snap/dotnet-sdk/current
export DOTNET_ROOT=/snap/dotnet-sdk-100/current/usr/lib/dotnet
```

Replace `100` with the SDK version you installed, such as `80` for .NET 8 or `90` for .NET 9.

### Export the environment variable permanently

The preceding `export` command only sets the environment variable for the terminal session in which it was run.
Expand All @@ -100,11 +91,13 @@ You can edit your shell profile to permanently add the commands. There are many
- **Korn Shell**: _~/.kshrc_ or _.profile_
- **Z Shell**: _~/.zshrc* or _.zprofile_

Edit the appropriate source file for your shell and add the export command for your installed .NET version. For .NET 9+, use `export DOTNET_ROOT=/snap/dotnet-sdk-100/current` (adjust the version number as needed). For .NET 8 and earlier, use `export DOTNET_ROOT=/snap/dotnet-sdk/current`.
Edit the appropriate source file for your shell, add the export command for your installed .NET version, and save your changes.

For example: `export DOTNET_ROOT=/snap/dotnet-sdk-100/current/usr/lib/dotnet`.

## 3. Use the .NET CLI
## 4. Use the .NET CLI

Open a terminal and type `dotnet`.
Open a terminal and run the `dotnet` command.

```dotnetcli
dotnet
Expand All @@ -130,27 +123,10 @@ To learn how to use the .NET CLI, see [.NET CLI overview](../tools/index.md).

## Troubleshooting

- [The dotnet terminal command doesn't work](#the-dotnet-terminal-command-doesnt-work)
- [Can't install Snap on WSL2](#cant-install-snap-on-wsl2)
- [Can't resolve the dotnet command or SDK](#cant-resolve-the-dotnet-command-or-sdk)
- [TLS/SSL Certificate errors](#tlsssl-certificate-errors)
Comment thread
adegeo marked this conversation as resolved.

### The dotnet terminal command doesn't work

Snap packages can map an alias to a command provided by the package. By default, the .NET SDK snap packages create an alias for the `dotnet` command. If the alias wasn't created or was previously removed, use the following command to map the alias.

For .NET 9 and later:

```bash
sudo snap alias dotnet-sdk-100.dotnet dotnet
```

For .NET 8 and earlier:

```bash
sudo snap alias dotnet-sdk.dotnet dotnet
```

### Can't install Snap on WSL2

`systemd` must be enabled on the WSL2 instance before Snap can be installed.
Expand All @@ -175,26 +151,8 @@ It's common for other apps, such as a code IDE or an extension in Visual Studio

Try the following steps to fix the issue:

01. Making sure that you [export the `DOTNET_ROOT` environment variable permanently](#export-the-environment-variable-permanently).

01. Try to symbolic link the snap `dotnet` executable to the location that the program is looking for.

Two common paths the `dotnet` command is looking for are:

- `/usr/local/bin/dotnet`
- `/usr/share/dotnet`

Use the following command to create a symbolic link to the snap package. For .NET 9 and later, use the version-specific package name:

```bash
ln -s /snap/dotnet-sdk-100/current/dotnet /usr/local/bin/dotnet
```

For .NET 8 and earlier:

```bash
ln -s /snap/dotnet-sdk/current/dotnet /usr/local/bin/dotnet
```
01. Complete [2. Map the dotnet command](#2-map-the-dotnet-command).
01. Set the `DOTNET_ROOT` environment variable permanently by following [Export the environment variable permanently](#export-the-environment-variable-permanently).

### TLS/SSL Certificate errors

Expand Down
Loading