← Default view
Linux Workstation Series · Distribution Selection Datasheet
DEV‑STACK‑2026

Six distribution families evaluated as a host for .NET 10 SDK, TypeScript/Node and Docker Compose, with Rider and VS Code on top.

Rev 2026.07 · Supersedes nothing
Tux, the Linux mascot
Fig. 0 — reference device, as shipped
DOC ATL/DTF-03
DATE 2026-07-30
DEPTH survey
REFS 39 cited
READ 15 min (canonical)
PARTS EVAL'D 6 families
SOURCE canonical page
FAMILY 8-angle framework
Key characteristics
  • There is no longer one "Microsoft .NET repo for Linux". Since .NET 9, packages.microsoft.com serves only distros that don't package .NET themselves [1]
  • 2 of 6 families install the .NET 10 SDK with zero added repositories [2][3]
  • Every distro-built SDK is locked to the .1xx feature bandA
  • The JS half of the stack is fully distro-neutralG
  • SELinux is the single largest practical difference for a Compose userC
Intended load
  • dotnet build / dotnet test, SDK 10.x
  • Node LTS + bun + pnpm, per-project versions
  • docker compose up against host bind mounts
  • Rider + VS Code, both reaching host toolchains
  • kubectl, Terraform, ssh to a Coolify homelab
  • PowerShell 7 as a second shell
Recommended part
Dual-sourced — functionally equivalent
UBU‑2604‑LTS≡
FED‑44

Both land at ΣREPO = 3 hand-configured vendor repositories and both are on all four vendor test listsD. They differ only in which tax you pay: Ubuntu costs you the .1xx-only SDK bandA, Fedora costs you a :z/:Z edit on every Compose volumeC.

Every other family in this datasheet costs at least one additional hand-configured repository, or drops off a vendor list entirely.

1

Setup-cost tally per part

ΣREPO = repositories you configure by hand and must re-fix at release upgrade
Ubuntu
26.04 LTS
UBU-2604-LTS
3
Docker
VS Code
HashiCorp
VENDOR 4/4
Recommended
Fedora
44
FED-44
3
Docker
VS Code
HashiCorp
VENDOR 4/4
Recommended
Debian
13
DEB-13
4
+ Microsoft
.NET feed
VENDOR 4/4
Conditional
Arch
rolling
ARCH-ROLL
0
repos — and
0 vendor support
VENDOR 0/4
Not rec.
openSUSE
Leap 16
SUSE-L16
4
worst vendor
coverage
VENDOR 1/4
Not rec.
Bluefin
DX (atomic)
BLU-DX
0–1
preinstalled,
3 new concepts
VENDOR 4/4 (via image)
Defer 12 mo
⚠ Absolute maximum ratings
Parameter Rating Result if exceeded
Registered .NET package feeds 1, max libhostfxr.so could not be found / missing FrameworkList.xml; tell-tale symptom is both /usr/lib64/dotnet and /usr/share/dotnet existing [6]B
:Z relabel target project dirs only Relabelling /etc, /usr or /var/lib breaks the host [21]
VS Code delivery channel deb / rpm / snap Flatpak sandbox sees no host toolchain and has no /var/run/docker.sock — kills Dev Containers, the .NET language server and every terminal dotnet/node call [28]I
Container engines bound to host ports 1, max Docker Desktop and Docker Engine conflict over port mapping; Desktop additionally needs KVM and GNOME/KDE/MATE [19]
glibc — Rider ≥ 2.28 Rider 2026.1 will not run [24]
glibc — bun ≥ 2.17 bun's glibc binaries will not run; unzip also required [16]
CPU ISA — bun default x64 build AVX2 Pre-Haswell CPUs silently get the slower baseline build [16]
kubectl repo minor-version drift 0 pkgs.k8s.io is pinned per minor version — the upgrade does not arrive until you edit the repo URL [30]J
Stresses beyond these ratings will not damage the hardware. They will consume the first weekend and produce error messages that do not name their cause.
ATL/DTF-03 · Rev 2026.07 Toolchain fit for .NET 10 + TypeScript + Docker, 2026 — 1 —
DEV-STACK-2026 · Toolchain characteristicsRev 2026.07
2

Toolchain characteristics

All values as of Jul 2026 · superscript letters index the notes on page 6
Symbol Parameter UBU-2604Ubuntu 26.04 LTS DEB-13Debian 13 FED-44Fedora 44 ARCHrolling SUSE-L16Leap 16 BLU-DXatomic
VSDK .NET 10 SDK source ✓ built-in feed
[2]		 +1 MS repo
[4]		 ✓ dnf
[3]		 ✓ pacman
[8]		 +1 MS repo
[5]		 inside a
container
FBAND Non-.1xx feature band obtainable from a package managerA ✗ [2] ✓ [4] ✗ [7] ✗ AUR -bin [8] ✓ [5] ✓ script in
container
RDOCK Docker Engine — availability and vendor supportE +1 vendor repo
✓ supported [18]		 +1 vendor repo
✓ supported [18]		 +1 vendor repo
✓ supported [18]		 ✓ pacman
✗ unsupported [20]		 ✗ unsupported
[18]		 ✓ preinstalled
[23]
ZMNT Existing Compose bind mounts work unmodifiedC ✓ ✓ ✗ needs :z/:Z
[21]		 ✓ ✗ ✗
IRIDE Rider — distro on JetBrains' tested list ✓ [24] ✓ [24] ✓ [24] ✗ off-menu ✗ off-menu ✓ Fedora base
ICODE VS Code — official first-party repoI ✓ deb [26] ✓ deb [26] ✓ rpm [26] ✗ AUR only [26] ✓ same rpm repo [26] ✓ preinstalled [23]
TFORM Terraform — first-party HashiCorp repo ✓ [32] ✓ [32] ✓ [32] ✗ AUR / mise ✗ [32] ✓
NJS Node / bun / pnpmG ✓ identical on every family — mise from ~/.local/bin, no distro involvement [15]
XMIX ⚠ .NET feed mix-up risk when adding the Microsoft repo for PowerShell 7B HIGH [6] none — same feed HIGH [6] HIGH [6] none — same feed contained
ΣREPO Hand-configured repositories 3 4 3 0 / 0 support 4 0–1
VEND Vendor test lists carrying this distroD 4/4 4/4 4/4 0/4 1/4 4/4
3

Part selection guide

What each part buys, and what it charges
Ubuntu 26.04 LTS
UBU-2604-LTS · ΣREPO 3
Fewest surprises, most documentation written against it, .NET 10 with no repository at all [2][38]. Pays with: old in-repo Node — 22.22.1 [12], irrelevant once you use mise — and a .1xx-only SDK bandA.
Fedora 44
FED-44 · ΣREPO 3
Same repository count, everything 6–18 months newer, dnf install dotnet-sdk-10.0 on day one [3][7]. Pays with: SELinux volume flags on every Compose fileC and occasional .NET package lag — RPM users hit No match for argument: dotnet-sdk-10.0 for weeks after the .NET 10 launch [9] ⭐ 3.2k.
Debian 13
DEB-13 · ΣREPO 4
The only family where Microsoft still ships .NET itself, so PowerShell and the SDK come from one feed with zero mix-up risk [4]. Pick it only if a repository pins a non-.1xx SDK band. Otherwise: one extra repo, and in-repo Node too old to matter.
Arch
ARCH-ROLL · ΣREPO 0
Freshest packages of anyone — Docker 29.6.2 within days, docker-compose 5.3.1, SDK 8/9/10 side by side [20][8]. Pays with: zero vendor support — absent from Microsoft's [1], Docker's [18], JetBrains' [24] and HashiCorp's [32] lists. When something breaks, you are the support.
openSUSE Leap 16
SUSE-L16 · ΣREPO 4
Microsoft supports it — and only Leap 16, never Tumbleweed [5]. Pays with: Docker, JetBrains and HashiCorp all absent [18][24][32]. Worst vendor coverage of the six. Skip for this stack.
Bluefin DX
BLU-DX · ΣREPO 0–1
The only atomic option where this stack is close to zero-config: docker-ce with Compose and Buildx, Podman tooling, and VS Code with Dev Containers already wired [23]. Pays with: Distrobox, Podman, SELinux and Flatpak learned simultaneouslyF — three unfamiliar layers stacked while Linux itself is new. Excellent destination, wrong starting point.
ATL/DTF-03 · Rev 2026.07 Characteristics measured against a .NET 10 / TS / Compose workload — 2 —
DEV-STACK-2026 · .NET 10 SDK sourcingRev 2026.07
4

Ordering information — .NET 10 SDK

Eight sourcing routes · who builds the binary matters more than the version string

This is the part that surprises Windows developers: there is no single "Microsoft .NET repo for Linux" any more. Since .NET 9, Microsoft publishes to packages.microsoft.com only for distributions that do not package .NET themselves — Azure Linux, Debian, openSUSE Leap and SLES. Alpine, CentOS Stream, Fedora, RHEL and Ubuntu ship their own builds [1], governed by a published selection policy [37] ⭐ 22k. Arch is on the "publishes its own" list too [6].

Part / host Order code Built by .NET 10 today ⚠ Friction
Ubuntu 26.04 LTS apt install dotnet-sdk-10.0 Canonical, built-in feed ✓ built-in [2] .NET 9/8 need ppa:dotnet/backports; SDK always .1xx [2]
Ubuntu 24.04 LTS apt install dotnet-sdk-10.0 Canonical ✓ built-in [2] Microsoft feed does not exist for 24.04+ [2]
Debian 13 packages-microsoft-prod.deb, then apt install dotnet-sdk-10.0 Microsoft [4] ✓ all supported versions One extra repo to register — the only family giving you non-.1xx feature bands from a package manager
Fedora 43 / 44 dnf install dotnet-sdk-10.0 Fedora / Red Hat ✓ 10.0.110 both [7] Microsoft explicitly warns packages can lag a .NET release [3]; RPM users saw No match for argument for weeks [9]
openSUSE Leap 16 add MS zypper repo, zypper install dotnet-sdk-10.0 Microsoft [5] ✓ Leap 16 only — Tumbleweed is not a supported .NET target; packages depend on OpenSSL 3.x [5]
Arch pacman -S dotnet-sdk Arch, source-built ✓ 10.0.10.sdk110 + 8/9/10 side by side [8] Not a Microsoft-supported distro at all [1]; other bands need AUR -bin rebuilds
Any distro dotnet-install.sh / tarball Microsoft binaries ✓ any version, incl. previews You install dependencies, export DOTNET_ROOT + PATH, and patch by hand. Microsoft: "for a developer or user, it's better to use a package manager" [10]
Any distro snap install dotnet-sdk Canonical [11] ✓ Snap confinement; fine for CLI, awkward alongside a distro installH
5

Failure mode FM-01 — dual-feed .NET installation

The one .NET failure this stack will actually meet
Trigger
Register packages.microsoft.com for PowerShell 7 on a distro that already ships .NET
Microsoft's repo is the documented, preferred PowerShell path [35] — so this is the normal path, not a mistake. Applies to Ubuntu 22.04+, Fedora, RHEL, CentOS Stream, Alpine and Arch [6].
▼
Symptom
✗ libhostfxr.so could not be found · FrameworkList.xml not found
Diagnostic: both /usr/lib64/dotnet and /usr/share/dotnet exist on disk [6].
▼
Mitigation
✓ Pin dotnet* away from the Microsoft repo on day one
apt: a preferences fragment with Pin-Priority: -10. dnf: excludepkgs=dotnet*,aspnet*,netstandard* in the repo file [6]. Debian and openSUSE Leap are immune — one feed serves both products.
Feature-band note Every distro-built SDK is .1xx: Ubuntu by Canonical policy [2], Fedora at 10.0.110 [7], Arch at 10.0.10.sdk110 [8]. A global.json pinning 10.0.2xx or 10.0.3xx is satisfiable only from Debian's Microsoft feed [4] or dotnet-install.sh [10]. Preview SDKs are in no package repository at all [3].
ATL/DTF-03 · Rev 2026.07 Since .NET 9, distro provenance decides which versions you can install — 3 —
DEV-STACK-2026 · Container subsystem & IDEsRev 2026.07
6

Container subsystem

Where distro choice actually costs you
Parameter Ubuntu / Debian Fedora openSUSE Leap Arch Atomic (Silverblue / Bluefin)
Docker Engine officially supportedE ✓ [18] ✓ [18] ✗ not listed [18] ✗ not listed [18] ✗ layer it yourself [22]
Docker Desktop officially supported ✓ both [19] ✓ [19] ✗ ⚠ experimental, untested [19] ✗
Distro-packaged Docker via Docker's own apt repo via Docker's own dnf repo zypper (community) pacman -S docker 29.6.2 + docker-compose 5.3.1 [20] Bluefin DX preinstalls docker-ce + compose + buildx [23]
Default runtime shipped Docker (after you add the repo) Podman preinstalled Podman neither Podman preinstalled
⚠ SELinux bind-mount frictionC none (AppArmor) ✓ real — :z/:Z or chcon -Rt container_file_t [21] ✓ none ✓
7

Functional block diagram — recommended sourcing layers

Identical on Ubuntu and Fedora, which is why they tie
Layer 0
base
Distro package manager — apt / dnf / pacman / zypper
Kernel, desktop, shells, C compiler. Not language runtimes: distro Node is behind and pinned for the release lifetime — Ubuntu 26.04 ships 22.22.1, 24.04 ships 18.19.1 [12], Fedora 44 ships nodejs22 at 22.22.2 [13].
▼
Layer 1
vendor
Vendor repositories — this is the ΣREPO count
Docker CE [18] · VS Code deb/rpm [26] · HashiCorp [32] · PowerShell 7 [35] · pkgs.k8s.io [30] · Microsoft .NET only where the distro doesn't build it [1]. ⚠ Each one is a .list/.repo file you re-fix at the next release upgrade.
▼
Layer 2
runtimes
mise ⭐ 31k — one config for node · bun · pnpm · kubectl · terraform
curl https://mise.run | sh → ~/.local/bin; also in apt, yum, brew, nix and snap [15]. Collapses four of the homelab-tooling rows into nothing and is byte-identical on every family.
▼
Layer 3
gap fill
Homebrew on Linux ⭐ 49k — optional, for the odd missing CLI
Single-user by design, needs a system C compiler and recent glibc/gcc, and uses sudo only during install [36].
⚠ SELinux gate — Fedora, Leap and every atomic image Compose bind mounts pass through an enforcing SELinux policy. Every host-path volume in your existing docker-compose.yml returns permission denied until it gains :z (shared) or :Z (private) [21] — edits to files you also hand to a Coolify-managed server that does not need them. Do not relabel /etc, /usr or /var/lib to work around it; :Z on those breaks the host [21].
Runtime selection Podman is the better security default and is preinstalled on Fedora and the atomic desktops, but Compose is Docker's home turf: you either run podman-compose ⭐ 6.2k or point the real docker compose ⭐ 38k at the Podman socket. With a homelab already standardised on Docker Compose: install Docker Engine and don't fight the distro default — cheap on Ubuntu/Debian/Fedora [18], a manual .repo drop plus a reboot on atomic [22]. Docker Desktop on Linux is mostly not worth it here: a KVM VM, a GNOME/KDE/MATE requirement, and a port-mapping conflict with Docker Engine [19].
8

IDE delivery channels

Rider and VS Code · channel choice is not cosmetic
JetBrains Rider
Fig. 2 — Rider
Tested on Ubuntu 24.04/26.04 LTS, Fedora 43/44, Debian 13, Amazon Linux 2023 [24]
Visual Studio Code on Linux
Fig. 3 — VS Code
Official deb, rpm and snap; the rpm repo also covers openSUSE/SLE [26]
Channel Rider VS Code
Recommended path ✓ JetBrains Toolbox tarball, unpacked to a directory you choose [25] ✓ Official deb or rpm repo [26]
Distros the vendor tests Ubuntu 24.04 & 26.04 LTS, Fedora 43/44, Debian 13, Amazon Linux 2023; glibc ≥ 2.28 [24] Debian/Ubuntu (deb); RHEL/Fedora/CentOS + openSUSE/SLE (same rpm repo) [26]
SnapH ⚠ available, but JetBrains flags "performance degradation" and points back to Toolbox [24] Official snap, auto-updates [26]
FlatpakI ⚠ exists, not the documented path [24] ✗ not an official channel [26] — and the sandbox is disqualifying, see FM-02 below
Arch / Nix AUR + Toolbox tarball Community AUR and nixpkgs builds [26]
⚠ Failure mode FM-02 — VS Code via Flatpak
The sandbox cannot see host toolchains, offers no easy way to install one inside it, and has no access to /var/run/docker.sock by default [28] — which kills Dev Containers, the .NET language server, and every dotnet/node invocation from the integrated terminal. Developer consensus on Lobsters is blunt: it "really shouldn't be the version suggested to users" [27]. Use the deb/rpm on a conventional distro, or a Distrobox/Toolbx container on an atomic one.
ATL/DTF-03 · Rev 2026.07 Containers and IDEs account for both recommended parts' entire cost difference — 4 —
DEV-STACK-2026 · Packaging ecosystems, runtimes, infraRev 2026.07
9

Packaging ecosystems — freshness vs breakage

Distro manager for the OS · vendor repos for .NET/Docker/PowerShell · mise for runtimes · brew for gaps
Ecosystem Dev-tool freshness Breakage risk Best used for
apt Ubuntu / Debian Slow for language runtimes — Node 22 on 26.04 [12]; fast for .NET on Ubuntu [2] Low — ⚠ vendor .list files break on release upgrade [2] The OS plus the vendor repos everyone else tests against
dnf Fedora Good — .NET 10 at 10.0.110 [7], 6-month cadence Low–medium — ⚠ .NET packages can lag a release by weeks [9] ⭐ 3.2k Current toolchains without rolling-release churn
pacman + AUR Fastest of all — Docker 29.6.2 within days [20], Ghostty in [extra] [29] Highest — AUR -bin packages are third-party rebuilds of vendor binaries People who want today's version and will read changelogs
zypper openSUSE Leap is conservative; Tumbleweed rolls but is unsupported by Microsoft [5] Low on Leap Not this stack — worst vendor coverage of the five
SnapH Good — official channels for VS Code [26], the .NET SDK [11] and kubectl [30] Medium — ⚠ JetBrains reports performance problems [24] GUI apps, not toolchains
FlatpakI Good for GUI apps ⚠ Actively harmful for dev tools — the sandbox hides host toolchains and the Docker socket [28] Slack, Spotify, browsers. Not IDEs
Homebrew on Linux ⭐ 49k Very fresh for CLI tools Low — needs a system C compiler and recent glibc/gcc, single-user by design [36] CLI tools missing or stale in the distro; no sudo after install [36]
Nix / nixpkgs ⭐ 26k Very fresh, reproducible per-project shells [39] Low for tools, medium conceptual cost; listed by Microsoft as a third-party .NET source [1] Per-project pinned environments — a big learning investment while Linux itself is new
10

JS runtime management — distro-independent

Ignore the distro entirelyG
Tool Stars (Jul 2026) Install path that works everywhere Notes
mise ◀ recommended ⭐ 31k curl https://mise.run | sh → ~/.local/bin [15] One tool for node, bun, terraform and kubectl via pluggable backends [15]; also in apt/yum/brew/nix/snap
fnm ⭐ 26k Single Rust binary Node only; fastest shell hook of the three
nvm ⭐ 94k Shell script Node only; measurable shell-startup cost
bun ⭐ 95k curl -fsSL https://bun.com/install | bash [16] Needs unzip and glibc ≥ 2.17; ⚠ default x64 build requires AVX2 — pre-Haswell CPUs silently get the slower baseline build [16]
pnpm ⭐ 36k Standalone script (no Node needed) or Corepack [17] Corepack/npm paths require Node ≥ 22 [17]
NodeSource ⭐ 14k Third-party apt/dnf repo [14] Only worth it if you want one system-wide Node managed by the package manager
11

Homelab & infrastructure tooling

Distro-neutral or vendor-repo-driven — only mildly penalises Arch and openSUSE
Tool Availability
Docker Compose ⭐ 38k Plugin from Docker's own repo on Ubuntu/Debian/Fedora [18]; pacman -S docker-compose on Arch [20]
kubectl pkgs.k8s.io apt/dnf/zypper repos, pinned per minor version — you edit the repo URL to upgrade [30]J; also curl binary, snap, brew
Terraform HashiCorp's own apt and dnf repos [31], covering Ubuntu, Debian, Fedora, RHEL/CentOS and Amazon Linux only [32] — ✗ no openSUSE, ✗ no Arch
OpenTofu ⭐ 30k Drop-in alternative if you'd rather avoid HashiCorp's licence terms
Coolify ⭐ 60k Server-side only; the installer supports Debian- and RHEL-based hosts [33]. Your workstation needs nothing but ssh + the docker CLI. For IaC, a community Terraform provider covers apps, databases, servers and env vars — the API is disabled by default, so enable it and mint a token [34]
PowerShell 7 Microsoft apt/dnf/zypper repos are the preferred path [35] — ⚠ this is the repository that triggers failure mode FM-01 [6]B
12

Terminal & shell

Least distro-dependent part of the whole exercise
Ghostty terminal
Fig. 4 — Ghostty
The one component on this page whose availability still depends on which distro you picked [29]
Component Distribution sensitivity
Shell None. bash by default everywhere; zsh and fish are one package install on every family
starship ⭐ 59k None. Consistent prompt across bash/zsh/fish, from a script or every distro repo
Ghostty ⭐ 59k ⚠ The one distro-discriminating terminal: first-party packages for Arch [extra], Alpine, Gentoo, Nix, Solus, Void and snap; Fedora needs a COPR and Ubuntu a community .deb; openSUSE dropped it over Zig versioning [29]
PowerShell 7 Install from Microsoft's repo [35] — but pin dotnet* away from that repo first [6]
ATL/DTF-03 · Rev 2026.07 Four decisions differ per distro; everything on this page does not — 5 —
DEV-STACK-2026 · Application note, notes, referencesRev 2026.07
Application note AN-ATOMICImmutable / image-based hosts
Bluefin project banner

The pitch: the OS is an image, your tooling lives in containers or $HOME, and a bad update is one reboot away from being undone. The cost for this stack is concrete.

  • rpm-ostree layering works, but it is not apt. Adding Docker CE on Silverblue means manually placing the .repo file in /etc/yum.repos.d/, then rpm-ostree install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin — and a reboot [22]. Fedora community members' first answer is "use the preinstalled Podman instead" [22].
  • Bluefin ⭐ 2.6k removes most of that. Its DX image preinstalls docker-ce with the Compose and Buildx plugins, Podman tooling, and VS Code with Dev Containers already wired to Docker [23]. If you want atomic, this is the version to try — the only atomic option where this stack is close to zero-config.
  • Distrobox ⭐ 13k and Toolbx ⭐ 3.4k become mandatory, not optional. Your .NET SDK, Node and CLI tools live inside a mutable container that the IDE reaches into — a genuinely new mental model on top of Linux itself.
  • ⚠ You inherit the SELinux tax and the sandbox tax at once. Podman default plus SELinux enforcing [21] plus Flatpak-first app delivery [28] is three unfamiliar layers stacked while bash is still new.
Verdict: excellent destination, wrong starting point. Revisit in a year.
13

Notes

Referenced by superscript letter throughout
A
Feature band. Every distro-built SDK sits in the .1xx band — Ubuntu by Canonical policy [2], Fedora at 10.0.110 [7], Arch at 10.0.10.sdk110 [8]. A global.json pinning 10.0.2xx/10.0.3xx is served only by Debian's Microsoft feed [4] or dotnet-install.sh [10]. Previews: no package repository, ever [3].
B
Feed mix-up (FM-01). Two registered .NET feeds produce libhostfxr.so / FrameworkList.xml failures, with both /usr/lib64/dotnet and /usr/share/dotnet present [6]. In practice it is triggered by adding packages.microsoft.com for PowerShell [35]. Mitigate on day one: apt Pin-Priority: -10, or excludepkgs=dotnet*,aspnet*,netstandard* in the dnf repo file [6].
C
SELinux volume flags. The single biggest practical difference for a Docker Compose user. Existing homelab docker-compose.yml files hit permission denied on bind mounts until every host-path volume gains :z (shared) or :Z (private) [21] — edits to files you share with a Coolify-managed server that does not need them. Never "fix" it by relabelling /etc, /usr or /var/lib [21].
D
Vendor test lists. The VEND score counts membership across the four vendor lists this stack depends on: Microsoft [1], Docker [18], JetBrains [24] and HashiCorp [32]. Which distributions get Microsoft .NET packages at all is set by a published selection policy [37] ⭐ 22k. Bluefin's 4/4 is inherited from its Fedora base and delivered through the image, not the host package manager.
E
Freshness is not support. Docker states plainly that it "doesn't test or verify installation on distribution derivatives" [18]. Arch's docker 29.6.2 and docker-compose 5.3.1 are the newest packages in this datasheet [20] and simultaneously the least supported.
F
Atomic layering. Docker CE on Silverblue needs a hand-placed .repo file, an rpm-ostree install of five packages, and a reboot [22]; Bluefin DX ships the same set preinstalled [23]. See AN-ATOMIC above.
G
The JS side is distro-neutral. Distro Node is always behind and pinned for the release lifetime — Ubuntu 26.04 at 22.22.1, 24.04 at 18.19.1, 22.04 at 12.22.9 [12]; Fedora 44 at 22.22.2 [13]. Neither gets you the current LTS line and neither lets you switch per project, so this whole axis drops out of the distro decision [15].
H
Snap. Official channels exist for the .NET SDK [11] and VS Code [26], but JetBrains reports performance degradation for IDE snaps and points back to the Toolbox tarball [24]. Treat snap as a GUI channel, not a toolchain channel.
I
Flatpak is disqualified for the editor (FM-02). No visibility of host toolchains, no easy way to install one inside the sandbox, and no /var/run/docker.sock by default [28]; it is also not an official VS Code channel [26]. Developer consensus agrees [27].
J
kubectl repo pinning. pkgs.k8s.io repositories are per-minor-version: upgrading to a different minor release means editing the version in the repository configuration [30]. mise avoids this by managing kubectl as a tool version instead [15].
14

Other datasheets in this family

Eight angles run independently against the same question
AN-01 · LANDSCAPE
The 2026 Linux distro landscape: what actually differs between the families
Only five real distro families; the honest shortlist is Fedora Workstation, Ubuntu LTS, Linux Mint, Bluefin/Aurora and openSUSE Tumbleweed.
survey
AN-02 · RELEASE MODEL
Stable, rolling, or atomic: picking a release model for your first Linux daily driver
Start on a 6-month fixed release or an atomic Fedora image; avoid pure rolling and avoid Debian stable.
survey
AN-03 · TOOLCHAIN — this sheet
Toolchain fit: which Linux distro costs least setup work for .NET 10 + TypeScript + Docker in 2026
Ubuntu 26.04 LTS and Fedora 44 tie on setup effort; every other family costs at least one hand-configured vendor repo.
survey · 39 refs · 15 min
AN-04 · DESKTOP
Picking a Linux desktop in 2026: the Windows 11 switcher's decision guide
KDE Plasma is the lowest-friction landing spot; X11 sessions die this year.
survey
AN-05 · HARDWARE
Hardware and driver reality in 2026: only three things should decide your distro
Only NVIDIA, very new silicon and Secure-Boot dual-boot still force a distro choice.
recon
AN-06 · MIGRATION
Windows to Linux in 2026: what crosses over, what doesn't, and how to stage the switch
Four things don't cross: desktop Office with VBA, a native Outlook with working calendar, WPF/WinForms designers, Windows-only compliance tooling.
survey
AN-07 · UPKEEP
Linux upkeep in 2026: support windows, upgrade pain, and monthly chores ranked
Atomic Fedora and Ubuntu/Mint LTS are near-zero chore; Arch costs a reading habit you cannot skip.
recon
AN-08 · GAMING
Gaming and media on Linux in 2026: singleplayer is solved, anti-cheat and DRM streaming are not
~90% of Windows Steam titles launch under Proton; kernel anti-cheat and 720p+ DRM streaming are the losses.
recon
15

References

39 sources · numbers match the bracketed markers throughout
[1]Install .NET on Linuxofficial · Microsoft Learn
[2].NET on Ubuntu: which feed to useofficial · Microsoft Learn
[3]Install .NET on Fedoraofficial · Microsoft Learn
[4]Install .NET on Debianofficial · Microsoft Learn
[5]Install .NET on openSUSEofficial · Microsoft Learn
[6]Troubleshoot Linux .NET package mix-upsofficial · Microsoft Learn
[7]dotnet-sdk-10.0 packageofficial · Fedora Packages
[8]dotnet packagesofficial · Arch Linux
[9]dotnet/sdk #52253 — No match for argument: dotnet-sdk-10.0forum · ⭐ 3.2k
[10]Scripted and manual .NET installsofficial · Microsoft Learn
[11]Install the .NET SDK snapofficial · Microsoft Learn
[12]nodejs across Ubuntu releasesofficial · Ubuntu Packages
[13]nodejs22 packageofficial · Fedora Packages
[14]nodesource/distributionsofficial · ⭐ 14k
[15]mise — Getting startedofficial · ⭐ 31k
[16]bun — Installationofficial · ⭐ 95k
[17]pnpm — Installationofficial · ⭐ 36k
[18]Install Docker Engineofficial · Docker Docs
[19]Install Docker Desktop on Linuxofficial · Docker Docs
[20]docker packagesofficial · Arch Linux
[21]SELinux and containersvendor blog
[22]Installing Docker on Silverblueforum · Fedora Discussion
[23]Bluefin DXofficial · ⭐ 2.6k
[24]Rider installation guideofficial · JetBrains
[25]Toolbox App installationofficial · JetBrains
[26]Visual Studio Code on Linuxofficial · Microsoft
[27]VS Code Flatpak is uselessforum · Lobsters
[28]The VS Code Flatpak problemvendor blog
[29]Ghostty — binary installationofficial · ⭐ 59k
[30]Install kubectl on Linuxofficial · Kubernetes
[31]Install Terraformofficial · HashiCorp
[32]Announcing the HashiCorp Linux repositoryvendor blog
[33]Coolify installationofficial · ⭐ 60k
[34]Coolify Terraform providerofficial · Terraform Registry
[35]Install PowerShell on Ubuntuofficial · Microsoft Learn
[36]Homebrew on Linuxofficial · ⭐ 49k
[37]dotnet/core #9556 — Linux distribution selection policyofficial · ⭐ 22k
[38]Ubuntu 26.04 LTS release schedulenews · OMG! Ubuntu
[39]NixOS/nixpkgsofficial · ⭐ 26k

DEV-STACK-2026 · Doc ATL/DTF-03 · Rev 2026.07 · issued 2026-07-30
Alternate presentation of Toolchain fit: which Linux distro costs least setup work for .NET 10 + TypeScript + Docker in 2026 — the canonical page is the source of truth and carries the full prose argument.
Angle 3 of 8 in Which Linux to switch to in 2026: a decision framework for a .NET developer leaving Windows. Index: Atlas.
Every characteristic in this sheet is traceable to one of the 39 numbered references. Version strings, star counts and package versions are as published in July 2026 and rot on their own schedule — re-read the vendor list before trusting a ✓.
ATL/DTF-03 · Rev 2026.07 End of datasheet — 6 —